Embracing Complexity in Serverless
summary
Distinguishes essential vs accidental complexity and shows how serverless services hide massive backend work using DynamoDB as an example, warns that enabling EventBridge cross-account targets can create a costly distributed monolith, and recommends decomposing by business domains into bounded contexts, applying an anti-corruption layer and designating a single domain bus account for publish/subscribe governance. Emphasizes refactoring, just-in-time architecture, small primitives and that these steps reduce inter-service communication lines and accidental complexity.
AI-written summary · about
chapters (7)
- 0:00Intro
- 4:05Agenda
- 4:58Acknowledging complexity
- 8:47Understanding complexity
- 12:58Managing complexity
- 26:22Closing thoughts
- 26:54Outro
related talks
23mSimplifying design complexities using Serverless Architecture on AWS
51mConfusion In The Land Of The Serverless
39mBuilding Highly Scalable Microservices with Serverless
52mConfusion In The Land Of The Serverless
55mConfusion In The Land Of The Serverless
30mEvolving Serverless Architectures
53mPatterns and practices for developing enterprise-scale applications with serverless
16mFrom Complexity to Clarity