Data Replication Explained

This article talks about replication and the need for data replication from one database to another or between systems. Every company has their own need to move data but the most common reasons for  data replication are as follows:
  1. Load reduction: Keeping a complete or partial copy of a collection on a different server reduces the load on the main server. 
  2. Improved service: Accessing a copy of the data can provide better service to users than having them access the original data.. 
  3. Restricted data access: If some users should only have access to a subset of data, replicating only part of a collection makes it easy to enforce security restrictions.
  4. Geographic distribution: Making only a subset of data relevant to a specific node (or location) available is beneficial in widely distributed enterprises (such as a chain of retail stores or warehouses). You can still make all data available at a central location for less frequent use.
  5. Disaster Recovery: Keeping a copy of the main data available allows for setting up rapid fail-over clusters (the capability to switch over to a redundant or standby computer server in case the main system fails). 
  6. "Cloud" computing: Replicating data allows for implementing what is commonly known as cloud computing (the on-demand storage, management, and processing of Internet-based data). 
During replication, a collection of data is copied from system A to system B, where A is known as the source (for this collection) and B is known as the target. A system can be a source, a target, or both (with certain restrictions). A complex replication topology has a number of sources, targets, and data collections defined. The replication process must account for the fact that source data may be changing while being copied. It is not possible to make or maintain copies instantaneously and to stop the source computer to “freeze” the information. Therefore, replication must account for:
  1. Integrity: The target data must reflect the complete result of all changes made to the source data during the replication process. 
  2. Consistency: If a change affects different tables, rows, or files, the copy must reflect these changes consistently across all affected tables, rows, or files. 
  3. Latency: The replication process must aim at keeping latency at a minimum. Ideally, it should not exceed a few seconds. 
Interested in working with me? I can be reached at pbaniya04[at] for any questions, consulting opportunities or you may drop a line to say HELLO. Thank your again for visiting my blog and looking forward to serving you more.

Have a Database-ious Day!


  1. Very interesting to read this article.I would like to thank you for the efforts you had made for writing this awesome article. This article inspired me to read more. keep it up.
    Best Data Science Institute In Hyderabad

  2. A very awesome blog post. We are really grateful for your blog post. You will find a lot of approaches after visiting your postdata science training in Hyderabad

  3. I've read this post and if I could I desire to suggest you some interesting things or suggestions. Perhaps you could write next articles referring to this article. I want to read more things about it!
    data science courses

  4. That's about as far as it goes for most users. Many don't even know what a hard drive looks like. Data Recovery Melbourne


Powered by Blogger.