ChaptersFoundations
Foundations
What makes a data system good? It should keep working when things break, cope as load grows, stay easy to change for years, and treat the people in its data fairly.
Not started
Reliability
Things will break. A reliable system keeps working anyway. What that means, where faults come from, and how good systems stop a fault from becoming a failure.
Scalability
"It scales" means nothing on its own. What grows, how you measure what users feel, why the slowest 1% decides everything, and how to add capacity when the load arrives.
Maintainability & architecture trade-offs
Most of a system's cost arrives after launch. What makes software easy to run, understand and change for years, how changes ship safely, and when to own the hardware.
Load Balancing
One address, many servers. How a balancer decides where each request goes, why the obvious choices backfire, and why two random guesses beat one perfect one.
Caching
The fastest request is the one you never make. How caches keep copies close, how they go stale, what they evict, and how a cache that's meant to protect your database ends up knocking it over.
Timeouts, Retries & Overload
Most big outages aren't caused by something breaking. They're caused by everything else reacting to it. How to give up gracefully, retry without stampeding, and stay useful when there's more work than capacity.
Doing the Right Thing
Every system that stores data about people makes ethical decisions, whether or not anyone meant to. What to collect, how long to keep it, how to really delete it, and how a model trained on yesterday learns yesterday's mistakes.