Event driven design and serverless
summary
Claims a production event-driven, serverless pipeline solves dependency and downtime by switching from synchronous callbacks to event transfer state and per-event functions; implementation uses AWS Lambda, API Gateway, NoSQL with change streams, a publish/subscribe broker and a managed state machine to enrich and classify events. Caching fixes 80–90% of availability hits. Warns about cold starts, timeouts, concurrency limits and observed Lambda throttling; the ingestion→processing→distribution pipeline is deployed and operating at Groupe SeLoger.
AI-written summary · about
chapters (4)
related talks
45mBuilding Event-driven Serverless Applications
23mSimplifying design complexities using Serverless Architecture on AWS
30mEvolving Serverless Architectures
39mServerless in production, an experience report
48mServerless design patterns
47mServerless in production, an experience report
01h 02mServerless in production, an experience report
43mBest Practices for Serverless Developers
