Frédéric Descamps is MySQL Community Manager for EMEA & APAC. He joined the MySQL Community Team in May 2016. "@lefred" has been an OpenSource and MySQL consultant for more than 15 years. His favorite topics are High Availability and Performance.
During this tutorial, attendees will get their hands on virtual machines and migrate standard Master - Slave architectures to the new MySQL InnoDB Cluster (native Group Replication) with minimal downtime. After explaining what Group Replication is and how it works (the magic behind it), we will experiment with multiple use cases to understand MySQL Group Replication. We will also get the attendees more comfortable with this new technology.
During our experiments, we will try to:
- Cleanly stop a node
- Kill a node
- Re-join a node
- Produce conflicts and see how the cluster behaves
- Create data inconsistency
- Recover from full cluster outage
Finally, we will check how we can integrate MySQL InnoDB Cluster with external routing solutions like ProxySQL. We will also see how to use what the cluster exposes to performance_schema and sys schema to make the right choice.
We will highlight the new improvements made in MySQL 8.0 regarding Group Replication and InnoDB Cluster.
Starting with MySQL 5.7 a new Document Store feature has been introduced that makes working with JSON documents an integral part of the MySQL experience. The new X DevAPI gives MySQL users the best of both worlds - SQL and NoSQL - and allows an entirely new category of use cases for managing data. It is constantly evolving based on the community feedback and can be run on top of the brand new MySQL InnoDB Cluster feature. This session gives a broad, high level introduction as to what the Document Store is about, its client components, the latest developments, what you can do with it, why you'd want to and how. MySQL 8.0 as Document Store will change the way people use MySQL.
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.