René founded ProxySQL in 2016 after developing it since 2013. He has over 15 years of experience as Database Administrator mostly on MySQL, working as Senior MySQL Support Engineer at Sun/Oracle, Senior Operational DBA at Blackbird, and consulting for small and large companies like Dropbox. In this period he build an analytic and problem solving mindset, he is always eager to take on new challenges, especially if they are related to high performance.
MySQL replication allows you to write on one writer server and easily scale out reads by redirecting reads to reader servers. But how do we guarantee read consistency with their last write? Galera replication can guarantee that, while MySQL Group Replication and standard MySQL async replication cannot.
If you are running MySQL Server or Percona Server, version 5.7 or newer, with GTID enabled, ProxySQL 2.0 is now able to ensure read consistently with the last write. ProxySQL is able to stream GTID information from all the reader servers, and in real-time is able to determine which reader server(s) is able to execute the SELECT statement producing a resultset that is read consistent with the last write (and GTID) executed by each client.
This presentation will show the technical details that allow you to build an architecture with thousands of ProxySQL instances and MySQL servers, and how GTID information is processed in real-time with limited bandwidth footprint.
ProxySQL is an open source proxy for MySQL that is able to provide high availability (HA) and high performance with no changes in the application, using several built-in features and integration with clustering software.
Those are only a few of the features you'll learn about in this hands-on tutorial.