Not necessarily focused on NoSQL, but a good read:
What concerns me is just the general impression I get from people, that nothing bad will happen to you if you just ignore it or pretend it’s not important. I good example of this is the latest new thing in devland: NoSQL databases. Rather than storing your data in the old-fashioned way, with tables and rows, now you can store objects or documents directly, using a growing variety of software that doesn’t function like a traditional database. While I’m a big fan of finding smart solutions to the object-vs-table problem, I do think a lot of developers are just happily thinking happy thoughts and avoiding complex (but more realistic) solutions like creating a proper relational database design. Instead they take the easy way out and use a NoSQL solution instead without properly considering whether it’s the right tool for their purposes, or if perhaps a traditional solution is better. I am by no means saying that NoSQL is bad (CouchDB is pretty awesome), just that we shouldn’t be blinded by all the (fake?) happiness and hype radiated by those who are promoting NoSQL products. Above all, be practical.
The opposite applies too. It would sound something like:
Rather than storing your data in the new-fashioned way, with documents or graphs, you should be spending a lot of time trying to push your data into the traditional database. But relational databases have been around for 30 years, so you’ll surely find a way to fit your data in, even if that object-relational mapping doesn’t make any sense to you.
Original title and link: Gurus and Bastards (NoSQL databases © myNoSQL)