Revolutions are endemic to tech culture. A new group comes along and wonders why the last generation built something so complex, and they set out to tear down the old institutions. After a bit, they begin to realize why all of the old institutions were so complex, and they start implementing the features once again.
We’re seeing this in the NoSQL world, as some of the projects start adding back things that look like transactions, schemas, and standards. This is the nature of progress. We tear things down only to build them back again. NoSQL is finished with the first phase of the revolution and now it’s time for the second one.
I’ve read an interesting article about NoSQL databases at infoworld. The article explains how the revolution of NoSQL databases have emerged and what the current situation from the perspective of solution development is. I think the article touches on important issues where NoSQL databases have inherent weaknesses besides their advantages, and every solution architect or developer must be aware of those issues.
To read the full article, please follow this link: 7 hard truths about the NoSQL revolution.