Message Brokers and Containers - the new ESB is “no ESB”
summary
Demonstrates building a message-driven identity system using Kafka, Docker and Azure Container Service on Mesosphere DC/OS plus an EventStore option, with a functioning demo: create user, failed logins (lock after four), unlock, password reset, and a separate history consumer that builds an audit table by replaying topics. Claims: keep messages as the archival source (keep messages forever), replay to rebuild state, use 80/20 current-state projections, archive older events (cloud streams often 30 days) and require durable audit writes.
AI-written summary · about
chapters (13)
- 0:00Introduction to the problem
- 1:28Evolution of hello world
- 2:50Why move to microservices?
- 5:43Barriers and magical tools
- 8:51The role of ESBs today
- 12:21Missing operational elements
- 16:13Designing microservices
- 19:47CQRS and data separation
- 23:24Events and state tracking
- 26:29Demo: Apache Kafka
- 35:27Building history projections
- 39:22Demo: EventStoreDB
- 45:57Conclusion and Q&A
related talks
01h 01mMessage Brokering and Event Driven Architecture on Azure
01h 05mGoodbye history tables, hello full audit- exploring message streams & event sourcing
01h 08mEvent Driven Architecture – Enabling Microservices
01h 11mEmbracing Messaging and Eventual Consistency in your Microservices Solutions
42mCreating event-driven microservices: the why, how and what
43mEvent Streams & Data Rapids: Harnessing the Full Power of Messaging Platforms.
41mGetting started with Event-Driven Architectures in 2023
57mEvent driven architectures on Azure