Scaling Twitter with MySQL

Best Practices for Businesses
4 April 3:00PM - 3:50PM @ Ballroom D

Experience level: 
Intermediate
Duration: 
50 minutes conference
MySQL is the data storage technology behind most Twitter data: the social graph, timelines, users, direct messages, as well as tweets themselves. With more than 200 million monthly active users and 500 million tweets per day, Twitter pushes MySQL and InnoDB a lot further than most companies. This talk will cover the data storage architecture at Twitter and how the architecture has evolved to meet Twitter’s needs. We will also discuss the challenges Twitter is facing in this area.


Speakers

Sr Engineering Manager, Twitter
Biography: 
Calvin Sun is senior engineering manager at Twitter, managing MySQL development. Prior to that, he managed the InnoDB team at Oracle. Calvin also worked for MySQL Inc. from 2006 to 2008, managing MySQL storage engines development. He has over 15+ years of database development experience.
Staff Software Engineer, Twitter
Biography: 
Inaam is a MySQL Internals Engineer at Twitter. Before joining Twitter, Inaam was a member of InnoDB team at Oracle. His area of focus has been performance and scalability of the InnoDB storage engine. He has been mostly working on the buffer cache layer, low level concurrency, IO subsystem and logging/recovery. Over the years, Inaam has had a chance to contribute to many scalability related features in InnoDB plugin, MySQL-5.5 and MySQL-5.6. In his previous work experience he had been involved in development of IBM’s DB2 LUW and PostgreSQL database engines. Inaam currently lives in Toronto, Canada.
Sr. Software Engineer, Twitter
Biography: 
Liang Guo is a core storage engineer at Twitter, mainly on improving MySQL/InnoDB. Prior to joining Twitter, he was a core database developer at Couchbase, working on data persistence engine and distributed system management. From March 2006 to April 2012, Liang was a principal MTS at the data storage engine team of Oracle database server, with extensive experience on transaction management, data storage format, data access path, flashback technology, etc.