Event-Driven Architecture - A successful strategy for a journey to the cloud
summary
A cloud migration implements an event-driven pipeline using Azure Event Hubs (Kafka endpoint), Azure Schema Registry, and Azure Blob Storage + Key Vault for encrypted blob storage; producers send keyed events to partitioned topics, three consumer groups (central site with two consumers, two regional single consumers) download blobs and emit download confirmations, and a cleaner deletes blobs only after all region confirmations. Authentication uses Azure AD client IDs/secrets with a cron rotating secrets; demo shows uploads succeed over simulated slow 3G.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker
- 1:51Customer's outdated architecture
- 4:21Agile integration explained
- 7:17Choosing cloud and tools
- 10:55Implementing the solution
- 18:20Adding security components
- 22:36Live demo of new architecture
- 27:43Q&A session
related talks
35mBuilding Event Driven Integration Architectures
51mImplementing an Event Sourcing strategy on Azure
52mEvent journal in Azure (no Cosmos inside)
43mDesigning software in the cloud
35mArchitectures and Trends for Event Stream Processing on Azure with Open Source Software
52mEvent journal in Azure (no Cosmos inside)
42mBuild a Real-Time Event-Driven Java Solution in Azure
41mA Case Study - Data Movement and Transformation using Azure Data Factory