Building Event-driven Serverless Applications
summary
Event-driven serverless shifts from API-driven one-to-one calls to asynchronous, one-to-many events so services scale and avoid cascading failures; examples show an e‑commerce order published to AWS EventBridge and routed to fulfillment, invoicing and forecasting with filtering, or queued in SQS/SNS for later processing. Implementation uses AWS Lambda (including Lambda Destinations), S3, DynamoDB, Kinesis and Step Functions; schemas register event shapes and the patterns are shown working end-to-end.
AI-written summary · about
chapters (24)
- 0:00Intro
- 2:23About me
- 3:19What is serverless?
- 10:29Different types of decoupling
- 13:17Commands versus Events
- 14:28Event-driven architectures drive reliability and scalabi
- 17:01Lambda can be invoked via three different methods
- 19:24AWS Lambda Event Destinations
- 20:29AWS Lambda - Destinations for Async Invocations
- 22:24Events enable interaction between services
- 24:37Let's launch an eCommerce site...
- 26:00Growing our business...
- 27:43Building an event-driven architecture
- 29:14Route orders to appropriate services
- 30:31Amazon EventBridge architecture
- 31:21Type of Event Buses
- 33:11Structure of an event
- 34:00EventBridge rules
- 34:44Writing patterns
- 35:43Targets
- 36:01Schema registry and discovery
- 37:17Common use cases
- 40:46Decoupled messaging
- 43:13Hands-on Workshop
related talks
37mBuild next-gen applications with event-driven architectures
23mSimplifying design complexities using Serverless Architecture on AWS
25mEvent driven design and serverless
49mBuilding Next-Generation Applications with EDA
31mAccelerate business innovation with serverless applications
38mEvent-driven Architecture
34mThinking serverless: From business problem to Serverless solution
30mThinking Serverless: From User Request to Serverless Solution