- How Booking.com avoids and deals with replication lag at 12.05
- Monitoring Booking.com without looking at MySQL at 15.30
Jean-François is working on growing the MySQL/MariaDB installations in Booking.com since he joined in 2013. His main task is focused on replication bottlenecks (and some other engineering problems too of course). Jean-François works on improving Parallel Replication and deploys Binlog Servers. He also has a good understanding of replication in general and a respectable understanding of InnoDB, Linux and TCP/IP.
In the fist talk, Jean-François doesn’t discuss about making replication faster, he will explain how to deal with the asynchronous nature of MySQL replication and therefore cover the (in-)famous lag.
During the session, he will start by quickly explaining the consequences of asynchronous replication and how/when lag
can happen. Then, Jean-François will present the solution used at Booking.com to avoid both creating lag and
minimize the consequence of stale reads on slaves (hint: this solution does not mean reading from the
master because this does not scale).
The second session is more different. I saw the first live presentation of it in Percona Live in Amsterdam and I really enjoy it. I don’t want to spoil it, so you will have to come to see Jean-François on stage sharing some “secrets” on how booking.com is monitored without looking at MySQL 😉