513 karma · joined March 23, 2009
http://www.xamuel.com/inverse-graphing-calculator.php?phrase...
But, I have no idea. Perhaps it is a bug wherein a CRLF is being added to the internal string? However, I highly doubt that.
http://highscalability.com/are-cloud-based-memory-architectu...
http://code.google.com/p/scalaris/wiki/FAQ#Is_the_store_pers...?
Anyway, this is a nice architecture indeed.
However, as a pure proxy, I would think nginx would be more appropriate for its (albeit poor but swappable) load balancing, rate limiting (a 3rd-party module), caching (memcache, redis), and general volume of usage.
In fact, there's the beginnings of a nginx upstream based redis module that supports redis' GET that could be made to RPUSH and BLPOP the result.
FWIW, I'm the author of redis-node-client. It should be noted that Promises were removed in favor of continuations in the latest Node.js on Github and I've updated redis-node-client appropriately. Thus, the sample code in the article is outdated by 2 days or so.
Using LPOP in a polling loop to wait for the response is not that great of an idea. It would be better to use BLPOP or "blocking left pop" which blocks the client connection (think "long polling") until there's something in the given list to pop. It does not waste resources and the results are returned in much less than the worst case (e.g. 100ms here). I haven't added BLPOP to redis-node-client yet though but it should be simple to patch.
To scale this beyond a single frontend, popFromQueue could potentially put the response back via LPUSH when the queuedRes[requestNumber] is nil... "Oops, this wasn't for me, let me put that back." Or, it could/should use something more formal.
Why does the Ruby worker shell out to redis-cli instead of using Ezra's client library?
Finally, "The previous spike..." What does "spike" mean here?
10. Late Night with David Letterman Theme
What?! I watch that show somewhat regularly and doubt that I would recognize it unnamed.You are assuming a lot here buddy. Save your preaching for Sunday school.
I have been working on my latest project for over a year, part-time. I tend to fall into the research trap as mentioned by some other posters. That is, once I learn how some giant puzzle of a project would come together I lose interest in the project. I suppose I like figuring out things instead of doing things. I am tired of this.
I ask because you have no scale-out capability given that all the users are stored in a simple JS object (great for a demo of course). Any plans on this front?
Rule 1 about being pissed off that someone told someone else something about you that you didn't want disclosed: do NOT make a big deal out of it. It just draws more unwanted attention.
It's tough to really love the thing without more information.
Oh, I love the comparison in sunlight to a macbook ... whose brightness was clearly turned down quite a bit.
I wrote up some comments elsewhere but this thread is more populated with people _using_ mongo in production.
Elsewhere = http://news.ycombinator.com/item?id=1110366