Replication on dbs
When two or more copies of data are stored in different places, it's called data replication.
Data replication is used for a variety of reasons:
Replication can be a complex topic, but we'll try to make it simple. Here's what you need to know about replication in relational databases.
As we said, replication is the process of copying data from one database to another.
In general terms, the source database is called the "master", and the destination database is called the "slave".
Based on the infrastructure and the design of our system, we can have different approaches:
Recommended by LinkedIn
Speaking of relational databases, we know that information is organized in tables (here is the article on relational databases), and replication can happen based on rows (when a row is updated, then the replication occurs) or based on the executed statement (when something happens, the replication occurs).
Which approach and kind of replication you should use depend on your situation; it's important to evaluate the pros and cons before proceeding.
For the moment, I hope it is clearer what replication is and that it is a very important aspect when your infrastructure grows (or needs to grow).
This series of articles is dedicated to managers who are not technical but need a quick introduction to technical topics from various subjects to be more aware in their work.