You Don’t Want to Build a Serverless Monolith
summary
Argument that serverless only helps if architecture and teams change: move from a monolithic database to small, bounded-data services, event sourcing and event-driven flows, and per-team ownership to avoid a distributed monolith. Demonstrates with AWS Lambda + Amazon API Gateway, S3 and DB triggers, a browser tool that emits SAM + CLI commands and builds a stack in minutes, and cites Monte Carlo runs that become 4x faster. Shows concrete CI/CD pattern (canary + business metrics), least-privilege permissions, and a working prototype that deploys and scales.
AI-written summary · about
chapters (11)
- 0:00Start
- 5:55Business Logic
- 11:15Kitchen Sink Analogy
- 14:44What Happens to the Data Flow
- 15:50Event-Driven Architecture
- 30:45What Is Recommended Way of System Integration Testing for Serverless
- 32:21What Differentiates the Architecture You'Re Proposing from Good Old Store Procedures and Triggers
- 33:41What Is a Bounded Context
- 34:01Microservice Architecture
- 35:09Independent Deployment
- 39:27Canary Deployments
related talks
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
51mTaking Serverless to the Next Level
39mBuilding Highly Scalable Microservices with Serverless
54mYou should be building Serverless Microservices
58mServerless - the brief past, the bewildering present, and the beautiful (?) future
04mServerless applications, Microservices, AWS
25mLeveraging Serverless in Full-stack Development
20mWhy Serverless Architecture is Changing Software Development