Module 9 of 10

Scalability & Resilience

Lessons

About This Module

A system that works for a hundred users can fall over at a hundred thousand, and any system that runs long enough will eventually see a server, a network link, or a dependency fail. A software architect plans for both: handling growth, and staying up when parts of the system break.

You'll start with horizontal and vertical scaling, the basic ways of adding capacity, then look at caching strategies for reducing load and latency. After that you'll cover the circuit breaker pattern for stopping one failing service from taking down others, and chaos engineering for testing resilience by causing failures on purpose.

Next up is Documentation & Leadership, where you'll look at how to communicate and record architectural decisions and guide teams to build them.

Lessons

4 videos
01

System Design Basics: Horizontal vs. Vertical Scaling

The difference between scaling up a single machine and scaling out across many, and the trade-offs each one brings.

02

Caching Strategies

Cache hits and misses, TTL, and the read-through, write-through, write-around, and write-back strategies.

03

Circuit Breaker Pattern: Fault Tolerant Microservices

How the circuit breaker pattern prevents cascading failures between microservices by failing fast.

04

How Chaos Engineering Works in Practice

What chaos engineering is, why teams break things on purpose, and how one company built its own tooling for resilience testing.