Limitations of Horizontal & Vertical Scaling | Day 17 | System Design series for Beginners

Scaling a system is not just about adding more resources. Both vertical scaling and horizontal scaling come with their own challenges and limitations, and understanding these trade-offs is essential for designing reliable and scalable systems. In Day 17 of the System Design Series, we take a closer look at the major limitations of both approaches. What we cover in this video: Vertical Scaling (Scale Up) We discuss the two major limitations: 1. Single Point of Failure — when your entire workload depends on a single machine, its failure can bring down the system. 2. Hardware Limitations — there is a practical ceiling to how much CPU, RAM, storage, and other resources a single machine can provide. Horizontal Scaling (Scale Out) We then explore two important challenges: 1. Data Consistency — with multiple machines handling requests, keeping data consistent across instances becomes more complex. 2. Fault / Partition Tolerance — distributed systems must continue operating even when communication between nodes fails or parts of the system become unavailable. Understanding these limitations helps us move beyond simply asking "How do I scale my application?" and start thinking about reliability, consistency, availability, and distributed-system trade-offs. This is Day 17 of the System Design Series, where we build our understanding step by step from the fundamentals toward designing real-world distributed systems. If you're preparing for Software Engineering or System Design interviews, make sure to follow the complete series. #SystemDesign #SystemDesignInterview #Scalability #HorizontalScaling #VerticalScaling #DistributedSystems #SoftwareEngineering #HLD #TechInterview #SystemDesignSeries #Codekerdos