Replication on dbs

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:

  • To keep data safe (for example, if one copy is lost or damaged, the others can be used to recreate it)
  • To help users access data faster (for example, if data is stored in multiple locations, users can access the copy that's closest to them)
  • To help systems keep running even if part of it fails (for example, if one database server goes down, the others can keep working)

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:

  • master/slave: where the master sends "fresh" data to the slave, which usually is used as a read-only replica;
  • master/master: where both are considered masters and both acts as read-write nodes. Obviously, in this case is critical the synchronization between the twos.

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).


No alt text provided for this image

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.

Feel free to propose new topics clicking here!

To view or add a comment, sign in

More articles by Simone Dall'Angelo

  • Analisi email 2024 e relativi insight

    Ogni anno guardo i 12 mesi precedenti cercando di vedere, dati alla mano, come sia andata la gestione delle email: ecco…

    5 Comments
  • ETF Bitcoin: 3 mesi dopo

    L'11 gennaio sono partite le vendite degli ETF "Spot" Bitcoin autorizzati dalla SEC. I principali ETF sono: IBIT:…

  • Comunicare il marchio con la voce degli intermediari: croce e delizia per il nostro brand

    Come non disperdere valore nella comunicazione online dei propri rivenditori o franchisee? Le aziende che si affidano a…

  • IT ⇢ Design: racconto di un percorso

    È il 2007, lavoro nella prima società che ho fondato con due compagni di classe e ci occupiamo di sviluppo IT. Siamo…

    1 Comment
  • Analisi email 2023 e relativi insight

    Nella mia giornata lavorativa la gestione delle email è un aspetto importante per non creare colli di bottiglia, ma al…

    2 Comments
  • Sul metaverso

    Per un po' sembrava che il metaverso sarebbe stata la grande nuova frontiera dell'innovazione e, anche qui su LinkedIn,…

    7 Comments
  • Blockchain: Come dimostrare qualcosa preservando la propria privacy?

    Come ormai abbiamo imparato, una delle caratteristiche delle blockchain è la loro trasparenza. In ogni momento, dato un…

    1 Comment
  • Defensive programming for non technical people

    When developers write code, they can apply different styles; today we talk of Defensive programming. Defensive…

  • Crypto domains for non technical people

    In one of the past articles, we talked about the Domain Name System (you can find it here). Today we talk about a…

  • Web servers for non technical people

    The whole internet experience we have daily is possible thanks to web servers. But what are they? How do they work?…

Others also viewed

Explore content categories