Horizontal Scaling

A great generic plan for scaling any app from zero to millions of users.

Single server setup
Selection and usage of database
Vertical scaling vs horizontal scaling approaches. And why you should prefer horizontal
Adding load balancer for horizontal scaling
Adding database replication for horizontal scaling
Adding cache
Adding CDN
Stateless vs Stateful architecture and using external state storage
Adding extra Data Centers
Adding Message queue
Adding Logging, Metrics, and Automation
Scaling database (sharding)
and futher steps…

All of these is carefully but briefly disclosed in the Chapter 1 of the book:

Earlier the book club of our company has studied excellent book:

Martin Kleppmann - Designing Data-Intensive Applications

This is the best book I have read about building complex scalable software systems. 💪

As usually I prepared an overview and mind-map.

Chapter 5:

Intro. How to scale apps. Replicating and partitioning.
Three algos of replicating
Single-leader Replication
- Leaders and Followers
- Sync and async replication
- Adding new Followers
- Handling node outages
- Technical implementations and all potential problems
Multi-Leader Replication
- Use-cases when it is good
- Handling write conflicts
- Three topologies and potential problems
Leaderless Replication
- Writing to the database when a node is down
- Quorums and problems with them
- Detecting concurrent writes and how to resolve them