\n\t| The change data capture of MySQL master is copied to binary log. MySQL Replication happens in three threads - dump thread in MySQL master continuously read binary log and send it to slave. IO thread in the slave receives the binlog that the master's dump thread sent, and writes it to a file called relay log. Another thread in slave, called the SQL thread, that continuously reads the relay log and applies the changes to the slave server.<\/td> | Certification based replication - Transaction ordering using group communication method, Optimal atomic execution of transaction in a single or multiple node (** We at MinervaDB don't recommend though inserts in multiple Galera Cluster nodes in parallel though) and during COMMIT a coordinated certification based process ensures transaction consistency across the cluster.<\/td>\n<\/tr>\n |
\n\t| In MySQL Master-Slave asynchronous replication, the UPDATES should always be done on one master, these are then propagated to slaves. Though It is possible to create a ring topology with multiple masters, We at MinervaDB do not recommended as it is very easy for the servers to get out of sync in case of a master failing.<\/td> | Every node in a Galera Cluster is always WRITE ready. Whenever a transaction commits, the row-based replication events are applied on all servers via a certification-based replication. In a certification-based replication, a transaction executes until it reaches the commit point, assuming there is no conflict. When a client issues COMMIT, Before actual transactional commit happens, the primary keys of keys of changed rows are copied into a write-set and sent to all other nodes. A deterministic certification test happens based on the primary keys on each nodes in the cluster, including the node where the write-set originated and determines whether the node can apply the write-set. If the test succeeds, the write-set ins applied to the rest of the cluster and transaction is committed. If the certification test fails, node drops the write-set and cluster rollbacks the original transaction.
\n <\/td>\n<\/tr>\n |