Personal schedule for Alexey Yurchenko
subscribe to Alexey Yurchenko's
Amazon engineers share experiences managing a large fleet of MySQL databases.
mysql> EXPLAIN SELECT * FROM CLOUDSQLDB
AND COUNT (CloudProviders)>1;
Come see a live demonstration of a highly-available and scalable cloud database – with self-healing, auto-scaling and pay-per-use – all with a click of a button.
Whether running with commodity servers on premise or in the cloud, there are many failure scenarios to protect your database against. In this session we will walk through the different types of replication possible with both self-managed MySQL deployments and managed Amazon Relational Database Service cloud deployments, understanding how they can help improve your availability and durability.
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.
Drizzle has thrown out the MySQL replication system and has started from scratch in implementing its own replication architecture. In this session, we'll take a look at the basics of the new architecture, what tools are available, and discuss possible future functionality. An example setup will also be presented.
Galera provides synchronous multi-master replication for MySQL/InnoDB. In a sense, it works like MySQL/Cluster but on top of InnoDB storage engine. Is this too good to be true?
Aside from traditional master-slave setup used mostly for HA and read scale-out, there is an established history of attempts at multi-master replication with MySQL. In this presentation we will look at what multi-master replication can do for us and compare different approaches of doing it.