System Design Basics: Scaling, Sharding, and the Trade-offs Architects Face

A startup's single-server API handled early growth well, but a viral surge tripled traffic and repeated vertical upgrades eventually hit a hardware ceiling. The resulting single point of failure caused a six-hour outage on the company's busiest day. The article explains that vertical scaling is simple but limited, while horizontal scaling has no fixed ceiling yet requires stateless applications and a different architecture. It also covers load balancing and the practical advice to scale vertically until costs rise, then design for horizontal distribution. The core message is that architectural choices must be made before traffic forces them.