"If all these new DBMS technologies are so scalable, why are Oracle and DB2 still on top of TPC-C? A roadmap to end their dominance."
The "roadmap to end their dominance" is very interesting: they have a new database model and prototype called "Calvin" that scales well with distributed transactions...
For the kind of application that TPC-C models ACID is non-negotiable, plain and simple.
It's one thing for there to be minor blips in data integrity to happen in the server's handling Google's search results or a social network's user data. But in a system that processes financial transactions, a blip in data integrity is an accounting error. An accounting error that could potentially expose the operator of the database system to serious financial harm or legal liability.
That. Why do some programmers --even on HN-- think that storing BS data for a social network has the same needs as storing life-and-death financial, medical, judicial, millitary etc data?
As far as data stability and accuracy needs go, social networks are at the very bottom of the pyramid...
I'm convinced that "NoSQL" really means "We found out how flipping difficult it is to write a decent query optimizer, so we didn't write one. Your on your own."
Otherwise, I cannot think of a reason to eschew the Standard Query Language as an interface to one's database product.
I'm skeptical about the NoSQL hype, too, but I don't think one can really write the whole thing off as fool's gold. If only because of examples like Google's success with BigTable.
"If all these new DBMS technologies are so scalable, why are Oracle and DB2 still on top of TPC-C? A roadmap to end their dominance."
The "roadmap to end their dominance" is very interesting: they have a new database model and prototype called "Calvin" that scales well with distributed transactions...