Webcast : SQL Diagnostic Manager for MySQL

Why and How To Go Multi-primary Over Regular Replication

Presenter: IDERA

Replication of MySQL servers is a process that allows data from one MySQL database server, known as the source or master, to be copied to one or more MySQL database servers called replicas or slaves. This process is asynchronous by default, meaning that replicas do not need to be connected to receive updates from the source. Replication can spread read access across multiple servers for better performance, higher availability, and other purposes such as failover.

Regular replication, also known as primary-secondary replication, in MySQL involves a single primary (source) server and one or more secondary (replica) servers. The primary server writes changes to the data in a special file called the binary log, and the replicas read from this log to update their data.

Multiple-primary replication (also known as multi-primary or multi-master replication) involves multiple primary servers that can all accept write operations. This configuration allows for increased write performance and better fault tolerance, as any primary server can handle write operations if another primary server fails. However, multi-primary replication can introduce complexities in handling conflicts and maintaining consistency across all primary servers.

Many replicate in a primary-secondary fashion, and you may be using asynchronous replication or semi-synchronous replication. However for extreme high availability without the need for an automated failover framework, the best way may be to go multi-primary (multi-master) replication where all this is built in. When is it right to migrate to such a replication scenario? What does your app need to know about this? Come to this webinar to learn about that, and we’ll also discuss how to easily monitor Galera Cluster metrics using SQL Diagnostic Manager for MySQL (formerly Monyog) in the 2nd half of the webinar!

Colin Charles is a Consultant at Codership, the makers of Galera Cluster. Previously, Colin was on the founding team of MariaDB Server, and has been around the MySQL ecosystem including being an early employee at MySQL, and worked actively on the Fedora and OpenOffice.org projects. Colin has been a MySQL user since 2000.

Shree Nair is Director of Technology Partnerships at IDERA. Shree has an exceptional track record in innovation, partner management, solution development, and global team leadership. He is the former Product Manager of Webyog’s MySQL tools. Under his direction, Webyog performed a complete overhaul of the product and business systems to target a wide range of industries worldwide and expanded customer base beyond 30,000 customers. Shree believes monitoring MySQL should be easy and he continually seeks opportunities to make MySQL user’s life easy. Shree earned a Master’s at Coventry University, England.

Topics : Database Monitoring,

Products : SQL Diagnostic Manager for MySQL,

Register for Free Webcast

Note: By filling and submitting this form you understand and agree that the use of IDERA’s website is subject to the General Website Terms of Use. Additional details regarding IDERA’s collection and use of your personal information, including information about access, retention, rectification, deletion, security, cross-border transfers and other topics, is available in the Privacy Policy.