MySQL InnoDB ClusterSet Concept and Architecture for Disaster Tolerance - Hananto Wicaksono

Today's landscape mandate for the IT to have the ability of its system to restore on an alternate cluster when the primary cluster fail. This disaster tolerance is conceptually an implementation of replication and failover from primary to alternate location, which the alternate location is typically located far away from the primary location. Through data replication, the secondary cluster will have an up-to-date data that are committed on the primary cluster. If the primary cluster fails, the secondary cluster will take over.
Due to long distance where network bandwidth and latency typically not suitable for a stretch out cluster. Thus, in MySQL, stretching InnoDB Cluster across two site is generally unfavourable due to performance and stability. Instead of using InnoDB Cluster, using InnoDB ClusterSet is a better option.
This talk will share about:
1. What is InnoDB Cluster and InnoDB ClusterSet
2. InnoDB ClusterSet architecture
3. Scenarios with InnoDB ClusterSet

Hananto Wicaksono
MySQL Master Princial Solution Engineer, Oracle
Hananto is a Master Principal Solutions Engineer at Oracle MySQL. He has 20+ years of IT consulting experience working as a Senior IT Architect and has extensive hands-on experience as a consultant and implementer primarily in systems and databases for Oracle and MySQL on Linux, Oracle SPARC, Windows, and Kubernetes.