Build next-gen applications with event-driven architectures
summary
Explains how event-driven serverless apps keep microservices decoupled by using Amazon EventBridge for rule-based routing and archiving plus schema discovery and AWS Step Functions as a scalable orchestrator with request/response, run-a-job and wait-for-callback patterns. Recommends implementing the saga pattern with compensating events, contrasts choreography versus orchestration, warns about sparse versus full event schemas, and shows a concrete example: a working Serverless Espresso workshop that demonstrates step functions and EventBridge coordinating order, payment and fulfillment.
AI-written summary · about
chapters (7)
- 0:00Introduction and welcome
- 1:47Why event-driven architectures matter
- 8:14Reducing coupling with events
- 14:14Saga patterns for consistency
- 18:01Amazon EventBridge overview
- 23:26AWS Step Functions deep dive
- 34:01Key takeaways and resources
related talks
45mBuilding Event-driven Serverless Applications
38mEvent-driven Architecture
32mChoreography vs Orchestration in serverless microservices
44mGetting started with Orchestration and Choreography in Distributed Applications
41mGetting started with Orchestration and Choreography in Distributed Applications
40mModernize your architecture: serverless and event‑driven
23mSimplifying design complexities using Serverless Architecture on AWS
56mDesigning Event-Driven Applications to Improve Scalability