Anyone can draw the boxes. Can you defend them?
Three classic systems, each solved end to end across Azure, AWS and Google Cloud — then put through the exact questions a review board throws at you.
The whiteboard is easy. The panel is not.
You've mapped the services and drawn a clean diagram. Then the room starts asking questions — the CFO taps the bill, the security lead hunts for the insider, the journalist asks why anyone should trust the system at all. This book is rehearsal for that room: the forces behind the design, and the answers that survive scrutiny.
Real systems, reasoned from first principles
Assumptions first, then the requirements that shape the system, then the cloud-neutral design — and only then the technology.
Social platform
Feeds, fan-out and the read/write trade-offs that decide whether it scales — or falls over at launch.
Online auction
Real-time bids, contention and correctness under load, where a lost update is a lost sale.
Election voting system
Integrity, auditability and trust — the design where "probably fine" is never good enough.
The same system, mapped to each provider
Every problem gets two diagrams per cloud — a logical block view and a deployment/network view drawn in that provider's own conventions, using its official service icons.
VNets, regions and managed services in Azure's idiom.
VPCs, availability zones and the AWS-native shape.
Projects, zones and GCP's deployment conventions.
The design-review simulator
Every chapter ends with the questions a sharp interviewer or difficult stakeholder actually asks — each with what they're really testing, the answer that lands, and the trap that fails the room.
"Why is this costing what it's costing?"
Tests: whether you know the cost drivers, not just the architecture.
"Show me how an insider breaks this."
Tests: blast radius, least privilege, and what you assumed you could trust.
"Why should anyone trust this system?"
Tests: auditability and the story you can defend in public.
Everything you need to reason — and defend
- 3 fully worked reference architectures — social, auction and voting, reasoned end to end.
- 18 diagrams — logical + deployment views per cloud, with official AWS, Azure & GCP icons.
- Assumptions, ASRs & defended trade-offs for every design — the reasoning, not just the result.
- The "questions you must survive" simulator at the end of each chapter.
Built for the people in the room
- →Architects preparing for design-session and whiteboard interviews.
- →Engineers who want to see the same problem solved three ways.
- →Anyone who has to defend a design in front of a review board.
Walk in able to defend every box.
Three designs, three clouds, and the questions you'll have to survive — the mindset that senior panels and review boards are really testing for.
"Learn the forces. The services are always in the docs."