Building Software Systems At Google and Lessons Learned

Jeff Dean walks through three generations of Google infrastructure and the numbers every backend engineer should know by heart.

distributed-systemsarchitectureperformance

Hamilton pulls back the curtain on the physics, power, networking, and custom silicon that make planet-scale cloud economically possible.

Harris revisits the SPA-vs-MPA argument through the lens of edge runtimes — and pushes back on the idea that SSR-everywhere is a victory for users.

Vogels makes the case that loose coupling and event-driven architecture aren't a style choice — they're how the world actually works.

Rich Harris pushes back on the SPA-vs-MPA dichotomy and sketches transitional apps — server-rendered, JS-enhanced, and progressively interactive.

Newman and Fowler talk through the cases where microservices earn their keep — and the much larger set where they don't.

Treat reframes consistency, latency, and partial failure as user-facing concerns — and shows what good distributed-system UX looks like.

Search the vault