4:25pm–5:10pm Wednesday, 04/13/2011
Google engineers have built a system that detects MySQL master failure, chooses a new master, promotes it and hooks up slaves with under a minute downtime. This is deployed in an environment where there's zero tolerance for transaction loss of any sort. The original designer and a sysadmin who worked on the deployment will talk about design, implementation and practical lessons learned.
5:15pm–6:00pm Wednesday, 04/13/2011
With contemporary web applications, data is never isolated to one store. Memcached has long been a partner to MySQL; now Membase, a persistent, replicated, clustered memcached-protocol-compatible datastore is used alongside MySQL for simple, fast key-value access. This session will dispel the idea of needing to choose between SQL or NoSQL, showing how you can be both rich and fast.
3:05pm–3:50pm Wednesday, 04/13/2011
At Twitter, we have gone through many iterations of storage systems as we have coped with tremendous growth. We have been able to solve many general distributed storage problems in a framework named Gizzard. This has allowed us to quickly and safely develop specialized components for the parts of Twitter that can no longer handle the scale at which they are required to operate.
11:55am–12:40pm Thursday, 04/14/2011
MySQL Cluster (NDB) is one of the most interesting storage engines. Oracle promotes NDB as the perfect solution for high volume transactions in high availability. On the other hand, many famous users are reluctant in migrating applications to NDB. This session will help in understanding in practical terms when it makes sense to use NDB and when it is better to stay with or use InnoDB.
10:50am–11:50am Wednesday, 04/13/2011
This session will introduce you to new MySQL Cluster features, its performance in benchmarks, and shows how major mobile phone and web companies build highly available real time solutions based on MySQL Cluster. Sometimes even with SQL.