Google高架构师Jeremy Cole谈大规模MySQL架构.pdfVIP

The MySQL Ecosystem at Scale Jeremy Cole Sr. Systems Engineer - SRE Google Inc. Jeremy Cole @jeremycole “Making MySQL Awesome” at Google Worked at MySQL AB 2000-2004 Contributor since 3.23 Over 14 years in the MySQL community Code, documentation, research, bug reports Yahoo!, Proven Scaling, Twitter Built a MySQL 5.5 fork at Twitter Attended XLDB many times but haven’t spoken before About this talk Not really about Google, per se Not academic or scientifically focused Pragmatic, from industry experience only Imperfect and non-ideal world MySQL’s roots High-scale usage scenarios Strengths and weaknesses at scale State and future of the MySQL ecosystem Databases in industry Always online, no downtime Low risk or carefully managed risk from operations Migration is the hardest part of any change No downtime, minimal impact from changes Usually 50-step online migration, not 2-step downtime Rollback must also be online Being up is much more important than being right The business is more important than good database principles Databases are fun Until you use them... A bit of MySQL history A short history of the MySQL software 1994: Development started; some roots already present 2000: 3.23 + InnoDB, replication 2002: 4.0 + replication redesign, set operations 2004: 4.1 + subqueries 2005: 5.0 + stored procedures, views, triggers, XA 2008: 5.1 + partitioning, row-based replication 2010: 5.5 + stability, code cleanup, InnoDB scalability 2013: 5.6 + InnoDB scalability, performance, manageability The MySQL commercial landscape 2003: Alzato (MySQL Cluster) acquired by MySQL 2005: Innobase Oy (InnoDB) acquired by Oracle 2006: Percona founded 2008: MySQL AB/Inc. acquired by Sun 2009: Monty Program (MariaDB) founded 2010: Sun acquired by Oracle 2010: SkySQL founded 2013: Monty Program acquired by SkySQL