Whenever updates are pushed to the master database, they are made to ripple through the slave databases in contact.

This replication process helps database administrators to replicate copies of the parent database to multiple servers simultaneously. And that’s where master-slave architecture comes in handy.īasically, master-slave databases involve caching data from the master database to the slave databases. To scale out your application, you need two data sources- one to handle the write operations and the other one to handle the read operations. Now if there is only one master database, then it will be overloaded, making the site slower for all your users. Imagine a situation where your site is bombarded with multiple data requests causing a surge in web traffic. This architecture is used to enhance the site's reliability to a greater extent. The reading operations are spread across multiple slave databases relative to the master database. The master database is actually the keeper of the data resources and also the place where all the writing requests are performed. The slave database serves as the backup for the master database. Pros of master-slave database architectureĪs the name suggests, the master-slave is a database architecture divided into a master database and slave databases.Steps to achieve master-slave replication.In this post, we will understand everything about this simple but widely useful concept. It has helped in the optimization of multiple databases. The master-slave design has been instrumental in alleviating system failures and performance issues. It revolves around producing seamless database connectivity between enterprises and their users. In fact, it has been in usage for quite some time now. Master-slave is not a new word in the world of databases.

Master db in sql server