Event Design & Event-first Development

on YouTube ↗38m

" summary

Argues that getting event schemas right up front avoids coupling, shows concrete AWS tooling: EventBridge for routing, Lambda and Step Functions for consumers, API Destinations for external integrations, and a real serverless espresso architecture used as an example. Distinguishes notification pattern (IDs only, consumers pull) from event carries state transfer (enriched payloads, easier filtering, eventual consistency headaches), recommends event storming, metadata headers like correlation IDs, producer-owned schemas, libraries for standardization, and a GitHub repo of event patterns and EventBridge examples.

AI-written summary · about

" chapters (13)

1. 0:00Intro
2. 1:12Adoption of EDA is growing
3. 5:06As you scale your EDA, problems start to emerge
4. 6:56Events design impacts your architecture
5. 7:28Agenda
6. 10:23Where do problems start?
7. 16:28How can event design help avoid common problems?
8. 16:52Understanding event patterns & tradeoffs
9. 29:00Which event pattern should you use?
10. 29:17Moving to event first thinking
11. 35:05Summary
12. 37:09Resources
13. 37:47Outro

" related talks

• 44mBuilding Distributed Applications with Event-driven ArchitectureEric Johnson · GOTO Chicago 2023
• 32mUnifying API and event driven architecturesWoody Rousseau · Craft Conference 2024
• 26mEvent-Based API Patterns and PracticesJames Higginbotham · AsyncAPI Online Conference 2020
• 46mManaging Event Driven ArchitecturesIan Cooper · Build Stuff 2021
• 40mEvent-Driven Integration Today & TomorrowJames Urquhart · GOTO EDA Day Nashville 2023
• 42mDesign Principles for an Event-Driven ArchitectureLuis Garcia, Pablo Ruiz · Commit Conf 2019
• 31mThe Power of Event-Driven Systems without Burning your Hands or BudgetsAllard Buijze · GOTOpia November 2020
• 42mApplication Architectures: The shadows and highlights of Event Driven DesignOskar Dudycz · 4Developers 2020