Distributed systems: Read Replication
Remember your users' data that are being read a lot.

Just a guy who loves to write code and watch anime.
Search for a command to run...
Remember your users' data that are being read a lot.

Just a guy who loves to write code and watch anime.
No comments yet. Be the first to comment.
Qualities that make outstanding builders.

Bipedal vs quadrupedal: how many legs This is about the number of legs the creature walks on. Bipedal. Two legs. Humans, ostriches, T-rex, kangaroos, most fantasy humanoids. Quadrupedal. Four legs. Do

Intro You hear "lerp" and "smoothstep" everywhere in game dev. They sound like math jargon. They're not. Both are small tools that do the same job: smoothly move from one value to another. The problem

What is Kinematics Kinematics is the math field. It's the study of how things move without worrying about forces (which would be dynamics). FK and IK are the two branches: forward kinematics and inver

Intro Textures are usually the biggest cost in a 3D scene. Memory, bandwidth, and load time all get eaten by them. Resizing them is the obvious lever. There's more. This post is about the less obvious

This article is the first part of my Distributed Systems series. I'm looking forward to writing about this as I'm learning about distributed systems at the moment.
Read replication is a solution for distributed systems that are read-heavy, but don't write a lot of data.
We would have a leader database, and then follower databases. The goal is to remember a specific value that has been sent by the client and written by the leader database.
This means every time someone wants to read specific data, they can get it right away, the cached version of it, from one of the follower databases.
If they write new data, that will take some time to get updated for the follower database, leading to a consistency problem. This means that the user could likely end up getting the stale value. Also, take into account, that the follower databases don't get updated at the same time, hence there will be some time during the update when they aren't the same.
This solution was invented early in web history since web architects discovered that there were lots more reads than writes to web traffic.
