Influence of Serverless in DDD
summary
Claims that serverless forces deployment to shape DDD models: functions are billed per invocation so pay for utilization drives designs toward fine-grained tasks instead of big cores, raising chattiness and cost when aggregates span contexts. Examples: EMR patient onboarding, AWS Cognito, CT-scan versus X-ray processing, and e-commerce search where visual AI or personalized recommendations are the true differentiators. Cites IDC +50% productivity, code delivers ~20% of business value while being ~5% of code, aggregates live ~200 milliseconds — so domain events as mini-aggregates become practical.
AI-written summary · about
chapters (11)
- 0:00Introduction and overview
- 0:47Serverless and strategic DDD
- 2:17Serverless as an integration tool
- 3:50Defining core business value
- 5:59Operational costs and efficiency
- 7:33Blast radius and fine-grained design
- 9:03Moving to tiny kernels
- 10:51Challenges of distributed models
- 13:13Deployment as a design influence
- 14:10Event-driven design
- 15:19Conclusion and paradigm shift
related talks
55mHow serverless impacts design -
01h 00mMicroservices and Serverless
39mBuilding Highly Scalable Microservices with Serverless
05mUnleash your DevOps with Serverless
28mServerless - the way microservices should be
35mServerless Experiences -- On Your Own Servers?
17mCloud Computing Made Better: An AWS View on Serverless Computing
28m8 Keys for Successful Serverless Architectures