I think there is a huge, huge gap between TwiDiBook's needs and the needs of the overwhelming majority of sites on the Internet. There are plenty of applications which do real things for real people which will <i>never</i> have scaling issues associated with them. The vast majority of the remainder of applications will have issues which are tractable by fairly simple solutions. And then we get to the pathbreakers who have to invent new methods of engineering to keep up with their growth curves.<p>The party is just getting started for "Hey, check it: we can put a cache in front of our database" for that broad middle of the curve. (This includes applications where relational databases are a great fit but for certain performance requirements in small bits of the program. For example, you <i>really</i> don't want to have to implement a university backend system in a key/value store. Just trust me on this one. It is virtually made for SQL, but while 99% of the use of the system is less than performance intensive, having resources in place to support that last 1% costs the university hundreds of thousands of dollars. I think we could slash that with creative caching.)
The Digg link said it best:<p><i>"Since it was already necessary to abandon data normalization and consistency to make these approaches work, we felt comfortable looking at more exotic, non-relational data stores"</i><p>In other words, to get MySQL to superduper scale, you have to turn it into NoSQL anyway. At which point, the only reason to be using MySQL at all is inertia, because it's pretty clunky compared to the other alternatives. Back in the day before Cassandra and etc, there wasn't a concept for NoSQL, and sharding MySQL looked like an exotic way of using a relational DB. Actually, no. It's a way of crudely emulating something that isn't a relational DB.
... I’m just suggesting do not just grab advice from the Internet or friends tip and do not complicate beyond the need. ...(Peter)
<a href="http://www.mysqlperformanceblog.com/2009/03/01/kiss-kiss-kiss/" rel="nofollow">http://www.mysqlperformanceblog.com/2009/03/01/kiss-kiss-kis...</a>