Patterns and practices for developing enterprise-scale applications with serverless
summary
Covers a real migration that puts an e-commerce backend 100% serverless e‑commerce backend on AWS and the engineering tradeoffs encountered: service quotas and throttling, cost and downtime risks, and cloud account separation. Shows concrete patterns—bounded contexts + Team Topologies, event bus choreography vs orchestrated flows using AWS Step Functions—and operational practices like idempotency, observability, and automation; practical, example-driven guidance rather than high-level platitudes.
AI-written summary · about
chapters (10)
- 0:00Introduction and welcome
- 6:09Serverless overview and mindset
- 15:45Enterprise scale complexity
- 20:26Problem decomposition with DDD
- 27:19Event-driven architecture patterns
- 36:16Event design and choreography
- 40:30Orchestration in serverless
- 43:16Sustainable development practices
- 48:15Cloud account separation
- 50:43Key takeaways and conclusion
related talks
45mPatterns & practices for developing enterprise-scale serverless applications
31mAccelerate business innovation with serverless applications
49mServerless Architectural Patterns and Best Practices
42mEnterprise Serverless Adoption. An Experience Report
38mServerless for the Enterprise
39mBuilding Highly Scalable Microservices with Serverless
40mCloud architecture patterns, how to implement them in a serverless way
14mThinking Twice About Migrating to Serverless