Implementing event-sourced microservices
summary
Skatteetaten rewrites its partsregister as event-sourced microservices using a small Java framework and an Oracle-backed central event store that assigns global sequence numbers so services can request consistent snapshots. The system persists incoming commands as events, produces enriched events, supports automated reprocessing with revisioned snapshots, and removes data via tombstones and compaction. It processes about 44 million events and proves to be operable at tax-authority scale while keeping reads scalable and writes serialized through the central store.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:00Agenda
- 2:21Event sourcing
- 8:30CQRS
- 9:41Domain
- 14:57Deficiencies
- 19:47Command sourcing
- 22:35Events
- 27:50Consistent monitoring
- 28:45Correcting errors
- 31:40Automation
- 33:22Event Store
- 34:16Deleting events
- 36:08Deleting state events
related talks
01h 25mBuilding microservices with event sourcing and CQRS
56mDeveloping Event-driven Microservices w/Event Sourcing and CQRS
35mA Reactive Architecture Approach for a Tax Information System Modernization
45mBuilding Event-Driven Microservices with Event Sourcing and CQRS
51mExperiences from large project maintenance at the Norwegian tax authority
48mEvent Sourcing - what could possibly go wrong?
29mEVENT SOURCING IN AKKA PERSISTENCE
31mA Path to Event Sourcing With Amazon MSK