Reactive Applications with Event-Sourcing and Server-Sent Events
summary
Explains how Axon Framework + optional Axon Server and Kotlin implement event sourcing with a live demo: a bank account aggregate handling create/deposit/withdraw commands via a Command Gateway, events stored in an event store, and an in-memory balance projection updated by event handlers. Shows async replication, subscription queries that push updates back to the UI, and a Spring Flux-based Server-Sent Events stream. Demo mostly works live (ran short on time before final SSE hookup).
AI-written summary · about
chapters (20)
- 0:00Introduction to the talk
- 1:25My background and career evolution
- 5:20Reactive Manifesto explained
- 7:04Understanding the CAP theorem
- 9:14Classic vs event-driven apps
- 11:22CQRS and event sourcing basics
- 15:18Axon framework overview
- 16:00Event sourcing in practice
- 18:28Event modeling and business alignment
- 19:34Command model implementation
- 22:04Query model and projections
- 23:27Consistency challenges in front end
- 24:53Message-driven updates with SSE
- 27:24Axon framework architecture
- 28:53Live coding demo setup
- 32:33Creating account command model
- 34:45Handling withdraw and deposit commands
- 39:19Building balance projection
- 41:30Subscription queries and SSE
- 44:01Q&A and closing remarks
related talks
43mUnraveling the Threads: Event-Sourcing, CQRS, and Event-Driven Architecture
26mEvent-Sourcing your React-Flux applications
49mEvent-Sourcing your React-Redux applications
01h 02mEvent Sourcing Loves Functional Programming
01h 04mState or Events? Which Shall I Keep?
50mAn Introduction to CQRS and Event Sourcing Patterns
47mPatterns for Building Event-driven Web & Mobile App Backends
22mGraphQL and CQRS, a Perfect Fit?