Truly, this is locking the barn door after the horse has bolted.

"The limited scalability of MySQL has therefore pushed it into relatively small database jobs or into clustered environments where large amounts of data need to be churned through."

are you out of your mind? since when people use mySQL for large amout of data in cluster environments? Teradata or Oracle Exadata are used for crunching TB+ data in cluster environements

"oracle mySQL 2010 family edition" anyone?

"Teradata or Oracle Exadata are used for crunching TB+ data in cluster environements"

Cluster environments can also be handy where you need guaranteed ability to handle lots of small transactions in real time. MySQL Cluster does exactly this (it was originally built by Ericsson people to handle phone+SMS billing).

> MySQL Cluster does exactly this

MYSQL cluster an in memory near real time database is awesome for certain classes of application. Accessed via a native C++ api it scales to handle near 100,000k transactions (reads/write) per second and offers atomicity, transparent node failover and multiple rendundency strategies including bi-site active-active replication configurations.

Mikeal is one of the developers - there's some interesting stuff on his blog -

http://mikaelronstrom.blogspot.com/2008/11/impressive-numbers-of-next-gen-mysql.html

"Truly, this is locking the barn door after the horse has bolted." Or maybe before the door closes. It could just be rushing to get features out before Orcale comes along and starts singing "it's my party, and you'll cry if I want you to". Or it could be the MySQL team trying to impress before the Oracle axemen get busy with the pink slips. Just imagine what it's like for all those other Sun hardware departments where Oracle hasn't stated any desire to proceed with their products - how do you impress your new overlords when you're the ones getting the blame for killing a Silicon Valley "legend"?