All these NoSQL posts are getting annoying. What I would really like to see are some real world numbers from companies using a NoSQL product and the challenges they faced(i mean other than digg and twitter, not at that scale). Perhaps even a follow up on how the solution works after 6 months of use.
Further, the companies that have both requirements know who they are, and don't need a "NoSQL movement" to get the right architecture in place; they just hire some good systems engineers who synthesize the useful concepts behind NoSQL from their actual requirements.
> the guy that ran the IT department for Walmart gave a presentation on how they got real-time data on each store.
http://news.ycombinator.com/item?id=1109385
> Any book on Walmart will talk about their IT systems. Their main operations room looks like NASA's mission control. I recall that Walmart can redirect trucks on the road via satellite to different stores whenever demand suddenly fluctuates.
A few takeaways that I got initially from Ted's post were that NoSQL isn't a magical cure for your backend problems, but instead is simply another solution that you may want to look into. Also, since most people won't be scaling at a point where the database becomes the technological limitation, it may be more worthwhile to examine your own code in the meantime.
Oh. And I resent the term "Rails-Lovin Ass-Clown"
For now, I have a new /etc/hosts entry that resolves to 127.0.0.1.
> in the old days, reads used to outnumber writes to the database 100 to 1. these days, it’s more like 7 to 1.
> ... in the last 14 days we’ve painfully had to scale from 44,000 daily uniques to 104,000 daily uniques.
Given the urban dictionary definitions, your "lifestyle" usage is far less common and probably not the intended meaning of the phrase in this article.
Everyone has an asshole, but only ~%10 of us are queer.