News for hackers. Stuff that matters.
Re:How We Built r/Place by nitwit005 on Thursday April 13, 2017 @02:52PM (#14109852)
Given the scale described, it sounds like they could have had a single machine that held the data in memory and periodically flushed to disk/DB to support failing over to a standby.
Re:How We Built r/Place by bsimpson63 on Thursday April 13, 2017 @02:55PM (#14109881)
You're basically describing how we used redis for this project.
Re:How We Built r/Place by nitwit005 on Friday April 14, 2017 @12:10AM (#14112656)
I suppose so, but then what did you gain from the extra hop to redis?
Re:How We Built r/Place by bsimpson63 on Friday April 14, 2017 @01:39AM (#14112884)
Not having to implement redis ourselves.
Re:How We Built r/Place by nullbyte on Thursday April 13, 2017 @09:23PM (#14112082)
Did you even bother reading the first few paragraphs? They talked about their usage of Redis for this. Next time please read the article before replying.
Re:How We Built r/Place by nitwit005 on Friday April 14, 2017 @01:35AM (#14112876)
Perhaps, rather than posting an insult, you should consider the possibility that you misinterpreted my comment?
Re:How We Built r/Place by Matheus28 on Thursday April 13, 2017 @08:12PM (#14111810)
I would be slightly more careful and just use a cluster of servers with a simple consensus algorithm (like raft). A simple C++ server with a raft library plus uWebSockets should be able to handle a lot of load.
Re:How We Built r/Place by foota on Thursday April 13, 2017 @02:56PM (#14109900)
That was my thought as well.