This is a first: a title change that is dramatically less informative than the original title. Please do not change the title of submissions. The guidelines are fairly clear on the policy and all you end up doing is making more work for "the ever vigilant deity of community goodness and truth in titling," aka dang.<p><pre><code> > please use the original title, unless it is misleading or linkbait.
</code></pre>
<a href="http://ycombinator.com/newsguidelines.html" rel="nofollow">http://ycombinator.com/newsguidelines.html</a>
Doesn't this point to a design issue with redis? The single threaded, blocking operation of it <i>works</i>, but it seems to present more problems than it solves for a large quantity of use cases. While it works, and works quickly for a narrow range of use cases, it comes at a huge loss in flexibility when compared to an SQL DB.<p>While I think it is possible to use redis well, I'm at a loss for what redis does for the <i>average</i> user, that a decent use of SQL doesn't do. My gut feeling is that if people would spend 30 minutes reading up on how to read a postgres query plan maybe they wouldn't reach for redis so quickly.