By Deane Barker | March 28, 2010 | 4 Comments
I Can’t Wait for NoSQL to Die: A nice rant against the NoSQL movement. I feel largely the same way. I concede there absolutely are situations where something other than a relational database is the right model, but they are very, very rare.
The idea is that object relational databases like MySQL and PostgreSQL have lapsed their useful lifetimes, and that document-based or schemaless databases are the wave of the future. Never mind of course that MySQL was the perfect solution to everything a few years ago when Ruby on Rails was flashing in the pan. Never mind that real businesses track all of their data in SQL databases that scale just fine. (For Silicon Valley readers, Walmart is a real business, Twitter is not.)
Boring as it might be, RDB technology is highly mature, and is the right choice most of the time.
Sounds like this guy has not actually had any real experience with a NoSQL database.
Here’s a good article by Joe Stump about this.
I don’t disagree with his points, but the examples he’s pointing to are all atypical. Very few people are Google.
Just choose the right tool for the job.
And for the case of monster databases… data partitioning and static data caching are your friends. Do you need to link everything to everything? In the case of facebook, do they need to have on hot storage every single message?