Pinboard (guardiantech)

Do Not Pass This Way Again >> grimoire

guardiantech — 2013-03-03T21:30:59+00:00

Considering MySQL? Use something else. Already on MySQL? Migrate. For every successful project built on MySQL, you could uncover a history of time wasted mitigating MySQL's inadequacies, masked by a hard-won, but meaningless, sense of accomplishment over the effort spent making MySQL behave.
Thesis: databases fill roles ranging from pure storage to complex and interesting data processing; MySQL is differently bad at both tasks. Real apps all fall somewhere between these poles, and suffer variably from both sets of MySQL flaws.

With examples.

How Twitter stores 250 million tweets a day using MySQL >> High Scalability

guardiantech — 2011-12-21T23:09:52+00:00

An all-time one to refer back to.

Facebook trapped in MySQL ‘fate worse than death’ >> Gigaom

guardiantech — 2011-07-19T13:14:11+00:00

"According to database pioneer Michael Stonebraker, Facebook is operating a huge, complex MySQL implementation equivalent to “a fate worse than death,” and the only way out is “bite the bullet and rewrite everything.”
"Not that it’s necessarily Facebook’s fault, though. Stonebraker says the social network’s predicament is all too common among web startups that start small and grow to epic proportions.
"During an interview this week, Stonebraker explained to me that Facebook has split its MySQL database into 4,000 shards in order to handle the site’s massive data volume, and is running 9,000 instances of memcached in order to keep up with the number of transactions the database must serve. I’m checking with Facebook to verify the accuracy of those numbers, but Facebook’s history with MySQL is no mystery."
You wouldn't really worry that you might become the world's biggest social network when you first typed "create database..."