Message Brokering and Event Driven Architecture on Azure

on YouTube ↗01h 01m

" summary

Compares Azure messaging choices with clear trade-offs and runnable code: uses Service Bus for ordered, transactional messages, Event Grid for push-style pub/sub, Storage Queues for cheap at-least-once work queues, and Event Hubs/Kafka for streaming; persists events to Cosmos DB and demos a three-API setup (students/classes/books) wired via Service Bus → Event Grid with a mediator library and hosted service. Also prototypes a full-stack, temporal datastore using xtdb demo, showing real-time client updates and practical limits like retention, ordering, idempotence.

AI-written summary · about

" chapters (8)

1. 0:00Event-driven architecture in Azure
2. 10:20Commands vs events
3. 17:23Choreography vs mediator
4. 24:01Event streaming & sourcing
5. 34:29Azure event-driven services
6. 41:55Demo: Azure services
7. 49:28Full-stack open-source events
8. 58:04Event-driven design pitfalls

" related talks

• 57mEvent driven architectures on AzureGraeme Foster · NDC Melbourne 2022
• 51mThis just happened! Using events in your appsGlenn F. Henriksen · Build Stuff 2019
• 55mImplementing scalable messaging patterns in AzureWill Velida · NDC Sydney 2024
• 55mMessage Brokers and Containers - the new ESB is “no ESB”Michele Bustamante · NDC Mini Copenhagen 2017
• 01h 09mExploring Flow ArchitecturesClemens Vasters · Visual Studio Live! Microsoft HQ 2022
• 45mCommon quandaries implementing your first Event Driven ArchitectureSarah Taraporewalla, Ann Mwangi · NDC Sydney 2020
• 46mPractical CQRS and Event Sourcing on AzureSander Molenkamp · Update Conference Prague 2018
• 01h 11mEmbracing Messaging and Eventual Consistency in your Microservices SolutionsMichele Bustamante · NDC Porto 2019