Events on the outside, on the inside and at the core
summary
Events act as the primary integration and consistency mechanism: services publish domain events instead of two‑phase commits so an order created -> credit reserved -> order open workflow enforces eventual consistency (example used order 4567 total $343 vs customer credit $12,000). Event sourcing becomes the primary persistence pattern: an append‑only event store plus snapshots, optimistic locking and idempotent handlers replace ORMs. Demo architecture uses angularjs + web sockets to push events from an event store to browsers, with denormalized read models in mongodb; the Kanban demo runs across AWS and shows realtime updates working.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:07About me
- 3:08Agenda
- 4:35Whats an event
- 6:51When events are produced
- 8:40Receiving events
- 13:58Webhooks
- 19:27Distributed Data Management
- 26:40Event Sourcing
- 37:46Benefits
- 42:45DomainDriven Design
- 48:51Java
- 49:39BAM Board
- 49:57Architecture
- 50:51Demo
- 52:02Summary
- 52:38Questions
related talks
03mEvents on the Outside, on the Inside, and at the Core
54mHow Events Are Reshaping Modern Systems
44mThe Dark Side of Events
48mEvent-Driven Architecture – Benefits and Pitfalls
47mComplex event flows in distributed systems
01h 08mEvent Driven Architecture – Enabling Microservices
54mDemystifying ‘Event’ Related Software Concepts and Methodologies
43mUnraveling the Threads: Event-Sourcing, CQRS, and Event-Driven Architecture