Building Highly Scalable Microservices with Serverless
summary
Claims that serverless reduces operational overhead and tames microservice complexity by using AWS primitives to decouple components, backed by a real refactor of a digital health system for 80+ million users. Architecture replaces a distributed monolith (shared backend-common library causing coupling) with business-bounded services (health record, onboarding, patient history, data exchange) using Serverless: Lambda, SNS, SQS, DynamoDB, API Gateway, CDK plus Event Storming and DDD. Uses fan-out + queue chaining, scatter‑gather aggregator, canary/blue‑green deploys; notes tradeoffs: data duplication, consistency limits (CAP), schema contracts, tracing and dead‑letter handling.
AI-written summary · about
chapters (11)
- 0:00🚀 Introduction to Building Scalable Microservices
- 4:00The Challenges of Microservices: Complexities in the Real World
- 7:30What Are Microservices and Why They Matter
- 12:00The Problems with Monoliths and the Need for Microservices
- 15:13A Real-Life Case Study: A Digital Health System
- 20:00Distributed Monoliths: The Pitfalls of Over-Engineering
- 25:10How to Successfully Implement Microservices with Serverless
- 28:00Event Storming and Domain-Driven Design for Microservices
- 32:00Managing Communication: Synchronous vs. Asynchronous Patterns
- 34:10Refactoring Monoliths with Serverless: The Right Approach
- 38:17Conclusion: Navigating Complexity and Ensuring Success in Microservices
related talks
23mSimplifying design complexities using Serverless Architecture on AWS
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
41mYou Don’t Want to Build a Serverless Monolith
28mServerless - the way microservices should be
01h 00mMicroservices and Serverless
31mAccelerate business innovation with serverless applications
54mYou should be building Serverless Microservices
58mServerless - the brief past, the bewildering present, and the beautiful (?) future