Distributed Consensus and Data Replication strategies on the server

We talk about the Master Slave replication strategy for reliability and data backups. This database concept is often asked in system design interviews with discussions on consistency and availability tradeoffs. Very closely tied to the master slave architecture is the concept of distributed consensus. When designing a system, we must make sure that the individual components can agree on a particular value. (Leader election, distributed transactions, etc...) Some popular techniques are 2 phase commit, Multi Version Concurrency Control, SAGAs and Quorum. Chapters 0:00 Problem Statement 0:53 Replication 1:24 Synchronous replication vs. Asynchronous replication 3:36 Peer to Peer data transfer 4:44 Split brain problem Also useful when used with Master Slave replication is sharding. You can check out the video mentioned below. Looking to ace your next interview? Try this System Design video course! 🔥 https://get.interviewready.io Course chapters: 1) Design an email service like Gmail 2) Design a rate limiter 3) Design an audio search engine 4) Design a calling app like WhatsApp 5) Design and code a payment tracking app like Splitwise 6) Machine coding a cache 7) Low level design of an event bus The chapters have architectural diagrams and capacity estimates, along with subtitled videos. Use the coupon code of 'earlybird' to get a 20% discount. References: Sharding:    • What is DATABASE SHARDING?   System Design Playlist:    • System Design Playlist   Designing Data Intensive Applications - https://amzn.to/2yQIrxH You can follow me on: Facebook:   / gkcs0   Quora: https://www.quora.com/profile/Gaurav-... GitHub: https://github.com/gkcs LinkedIn:   / gaurav-sen-56b6a941   #SystemDesign #Databases #Replication