Introduction to distributed systems
summary
Starts from a single-server web app, shows adding cache, moving to a dedicated DB server, then horizontal load‑balanced backend nodes; explains tradeoffs of vertical scaling vs horizontal scaling, session stickiness (consistent routing) and why local state is risky. Details database strategies: master–slave with majority‑ack replication versus slow full sync, and hash‑based sharding to split reads/writes. Ends with microservices owning separate DBs and using Kafka/Hermes event streaming to decouple services and guarantee delivery.
AI-written summary · about
chapters (9)
- 0:00Start
- 11:51Vertical Scaling
- 12:20Load Balancer
- 14:14Auto Scaling
- 15:23Master Slave Architecture
- 22:28Hash Table
- 23:59Hash Functions
- 33:31Is microservices a Way of Scaling Application
- 34:48Event Streaming
related talks
30mDistributed system design
44mDistributed systems and scalability rules
34mDistributed systems 102
02h 18mDistributed Systems: In the Daily Life of the Data Engineer
25mGrowing Distributed Systems
28mPractical Approaches To Scaling Distributed Transactions
58mElements of Distributed Architectures
29mFollowing the Data: A Deeper Look into Distributed Applications