Chapter Ten
Case Studies
Five workload shapes, each producing a different architecture from the same service catalog. The point is not the specific stack but the reasoning — which requirements drove which choices.
Each case study starts from requirements — traffic shape, compliance, latency, budget — and reasons toward an architecture, naming the services from earlier chapters and the trade-offs behind each pick.
Read them as worked examples, not blueprints to copy. The same five problems on different constraints would produce different stacks; the transferable skill is the reasoning.
Services in This Chapter
Service 66
E-commerce Platform
A high-traffic retail system — catalog, cart, checkout — and the autoscaling, caching, and resilience it demands during a traffic spike.
Service 67
Fintech Application
A regulated financial workload where security, auditability, and data integrity dominate every architectural choice.
Service 68
Data Analytics Pipeline
Ingest, store, transform, and analyze at scale — from streaming events to a queryable warehouse.
Service 69
Microservices Migration
Decomposing a monolith and moving it to AWS — the strangler pattern, containers, and the order of operations.
Service 70
Serverless SaaS Application
A multi-tenant SaaS built without managing servers — tenant isolation, per-tenant cost attribution, and scaling to zero.