MySQL replication
MySQL replication is used when single server is not sufficent for the safe and smooth service and MySQL cluster is not by design suitable for actual solution.
![](/images/schema/schema-7/images-02.png)
![](/images/schema/schema-7/images-02.png)
![](/images/schema/schema-7/images-02.png)
![](/images/schema/schema-7/images-02.png)
![](/images/schema/schema-7/images-03.png)
write
![](/images/schema/schema-7/images-04.png)
read
![](/images/schema/schema-7/images-05.png)
![](/images/schema/schema-7/images-01.png)
Common reasons to deploy replication usually are:
- request for high availability
- preventing blocking operations at sql servers from affecting the application
- load balancing
Virtis s.r.o. company implements replication in serveral different scenarios:
- slave server meant for backup
- master master replication with consistency checks and load balancing mechanism
- master slave replication in a classical implementation (see fig) for more demanding web projects
- hybrid implementation of above mentioned scenarios in various combinations