Tuesday, October 18, 2011

The “slave” term has been used in MySQL because the Slave servers have to perform every task in copying from the Master binlog, then updating their relay logs and finally committing to the Slave databases. The Master plays no role in replication here other than storing the replication events in the binlog.

With this kind of Master- Slave set up, there are several limitations-

-Slave lag

-Stale or old data

-Data loss

-Manual failover which is error-prone and time consuming

In SchoonerSQL, there is no concept of “Slaves” inside synchronous cluster. We refer to it as "Read Masters" because of our synchronous approach and different replication architecture. It is through push mechanism of replication events coupled with faster processing of multiple parallel threads.

This ensures that that Master and all Read Master’s data in a synchronous cluster are always consistent. So you can insert the data in a Master and at the same time query it on our Read Masters for any latest updates.

SchoonerSQL Synchronous Replication Architecture

Schooner's approach provides several benefits:

·Zero Data Loss

·Guaranteed Data Consistency across all nodes

·No Stale Data

·Zero Lag

·Faster Response Time than traditional MySQL

·Auto failover to any of the nodes in the cluster as the data is consistent & transparent to the user thereby achieving full service continuity.

This type of replication is very useful for Websites or Enterprises looking for a truly synchronous solution of MySQL-InnoDB with no lag.

About Me

Expert in product, technical,sales,marketing and strategies.
Want to know more about my present company Schooner which provides five 9s availability with no slave lag?
http://www.schoonerinfotech.com/about_us/contact_us