Exploring Flow Architectures
summary
Explains concrete patterns and product choices: Azure runs about 7 trillion requests per day, with ~90% on Event Hubs; Event Hubs act as capture for raw event streams while Event Grid does push routing and Service Bus or SQS-style queues provide exclusive job ownership. Shows a live use case: stadium ticket sync implemented by two devs in three weeks (now repeatable in a week) using Eventim webhooks, queues and ERP integration. Describes CloudEvents, a CNCF schema/registry and an event horizon where streams turn into indexed databases.
AI-written summary · about
chapters (22)
- 0:00Introduction to messaging
- 1:11Event-driven architecture
- 2:30Defining events and flows
- 4:23Imperative vs. event-driven
- 8:41Hybrid system architectures
- 11:06Real-world integration case
- 14:23Extensibility in practice
- 17:31Event data utilization
- 19:31Signals, events, and jobs
- 22:25Contextualizing signals
- 24:30Hierarchical event data
- 27:00Actionable vs. analytic events
- 30:33Event routing infrastructure
- 33:51Queues versus event streams
- 36:51Timeliness and latency
- 38:34The 'catching rain' pattern
- 42:35Databases and event sourcing
- 46:46Stream processing logic
- 51:12Demo: No-code stream capture
- 57:54Standardizing events
- 1:00:24Discovery and catalogs
- 1:07:34Conclusion
related talks
51mThis just happened! Using events in your apps
55mImplementing scalable messaging patterns in Azure
57mEvent driven architectures on Azure
37mBuilding Event-driven Apps at Scale
01h 01mMessage Brokering and Event Driven Architecture on Azure
40mEvent-Driven Integration Today & Tomorrow
51mComplex Event Flows in Distributed Systems
38mMessaging Patterns to Transform Your Cloud Architecture