Common quandaries implementing your first Event Driven Architecture

on YouTube ↗45m

" summary

Teams migrate a refactored monolith to event driven architecture using Azure Event Hub (with a planned Kafka path) and sometimes simpler atom feeds for early rollout, run local Kafka in Docker for development, adopt event sourcing + CQRS with snapshots tuned from 100 to snapshots every 10 events to fix replay performance, and enforce a correlation id and log pattern for observability. Choices include Azure Event Hub vs Kafka, Axon or framework mediators, and pragmatic async commands.

AI-written summary · about

" chapters (18)

1. 0:00Intro
2. 2:29Microservices
3. 3:04REST API
4. 5:17Why Now?
5. 8:54What is Event Driven Architecture?
6. 9:20What is in the Box?
7. 10:26Domain Driven Design
8. 12:11Event Sourcing
9. 16:43What Technology Should We Use?
10. 21:18What is an Event?
11. 22:14Grouping Events on Separate Streams
12. 24:18Beware of Passive Aggressive Events
13. 27:02How to Develop and Test?
14. 31:50How to Slice the Work?
15. 33:45Observability
16. 37:05Performance
17. 40:02Availability
18. 42:23Reporting and Analytics

" related talks

• 39mEvent Driven Architecture: From Ideation to ProductionSarah Taraporewalla, Ann Mwangi · XConf Online Australia 2020
• 01h 08mEvent Driven Architecture – Enabling MicroservicesBrad Irby · Silicon Valley Code Camp 2018
• 57mEvent driven architectures on AzureGraeme Foster · NDC Melbourne 2022
• 01h 01mMessage Brokering and Event Driven Architecture on AzureMarilag Dimatulac Svennevig · NDC Sydney 2022
• 31mDemystifying Event-Driven ArchitecturesBogdan Sucaciu · Conf42 Enterprise Software 2021
• 41mGetting started with Event-Driven Architectures in 2023Dennis Kieselhorst, Maximilian Schellhorn · Øredev 2023
• 48mEvent-Driven Architecture – Benefits and PitfallsRamanan Natarajan · Developer Summit 2020
• 26mImplementing Event-Driven Microservices Architecture (...)Nikhil Barthwal · Lambda Days 2017