Designing Data-Intensive Applications – Single Leader Replication

We dive back into Designing Data-Intensive Applications to learn more about replication while Michael thinks cluster is a three syllable word, Allen doesn't understand how we roll, and Joe isn't even paying attention.

For those that like to read these show notes via their podcast player, we like to include a handy link to get to the full version of these notes so that you can participate in the conversation at https://www.codingblocks.net/episode160.

Sponsors

• Datadog –  Sign up today for a free 14 day trial and get a free Datadog t-shirt after creating your first dashboard.
• Linode – Sign up for $100 in free credit and simplify your infrastructure with Linode's Linux virtual machines.
• Educative.io – Learn in-demand tech skills with hands-on courses using live developer environments. Visit educative.io/codingblocks to get an additional 10% off an Educative Unlimited annual subscription.

Survey Says

How important is it to learn advanced programming techniques?

Take the survey at: https://www.codingblocks.net/episode160.

News

• Thank you to everyone that left us a new review:
  • Audible: Ashfisch, Anonymous User (aka András)

The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair Douglas Adams

Douglas Adams

In this episode, we are discussing Data Replication, from chapter 5 of "Designing Data-Intensive Applications".

Replication in Distributed Systems

• When we talk about replication, we are talking about keeping copies of the same data on multiple machines connected by a network
• For this episode, we're talking about data small enough that it can fit on a single machine
• Why would you want to replicate data?
  • Keeping data close to where it's used
  • Increase availability
  • Increase throughput by allowing more access to the data
• Data that doesn't change is easy, you just copy it
• 3 popular algorithms
  • Single Leader
  • Multi-Leader
  • Leaderless
• Well established (1970's!) algorithms for dealing with syncing data, but a lot data applications haven't needed replication so the practical applications are still evolving
  • Cluster group of computers that make up our data system
  • Node each computer in the cluster (whether it has data or not)
  • Replica each node that has a copy of the database
• Every write to the database needs to b