Many, said Oskarsson, had even dumped the open-source MySQL database, a long-time Web 2.0 favorite, for a NoSQL alternative, because the advantages were too compelling to ignore.
Again, context is key here. What's the value of the data in question? What if the data isn't always consistent? User profile or deposit/withdrawal data is of higher value, with a higher requirement for consistency than voting data from a Web site poll.
As the MonoDB guys say:
Databases are specializing - the "one size fits all" approach of the RDBMS no longer applies.
But this doesn't mean approach Y will completely displace approach X. I'm reminded of the open source (Y) versus traditional software (X) argument. Far from Y killing X, we're settling in on a software industry where both models are appropriate, depending on the use case.
Vendors that can bridge the gap between RDBMS and the NoSQL movement are going to be the winners.
The proponents of NoSQL are too early in the game and may indeed be too heavily invested in differentiating from RDBMS that they will pay little attention to this bridge. Traditional RDBMS vendors would prefer that customers use RDBMS products to address these extremely high-volume, low-value data scenarios that the NoSQL movement is better suited. SpringSource's Javier Soltero nails this sentiment:
Oracle would tell you that with the right degree of hardware and the right configuration of Oracle RAC (Real Application Clusters) and other associated magic software, you can achieve the same scalability. But at what cost?
Enterprises need to be shown that both the RDBMS and NoSQL approaches have their place and can both be applied to drive business benefit. IBM, Oracle, Microsoft, you listening?
Follow me on Twitter at: SavioRodrigues.
p.s.: I should state: "The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions."