Building microservices with event sourcing and CQRS

on YouTube ↗01h 25m

" summary

Explains how combining CQRS with event sourcing stores every state change as immutable events (JSON preferred), lets teams rebuild state to any timestamp, run event replay for debugging, and support temporal queries; recommends lightweight brokers like RabbitMQ and read stores such as Hazelcast or Neo4j; describes optimistic versioning for concurrent updates, anonymization instead of deletion for regulation, checkpoints/snapshots to avoid full replays, and points to Axon and Akka Persistence as practical starting toolsets.

AI-written summary · about

" chapters (13)

1. 0:00Intro
2. 4:58Drawbacks
3. 11:58Example
4. 13:53Naming
5. 17:14Finegrained events
6. 20:00Treating events immutable
7. 22:31Legacy systems
8. 23:21Enterprise Service Bus
9. 28:28Business Value
10. 31:08CQRS
11. 32:56Refactoring
12. 45:44Consistency risks
13. 50:57Consistency

" related talks

• 56mDeveloping Event-driven Microservices w/Event Sourcing and CQRSChris Richardson · Philly ETE 2015
• 17m7 Reasons why your microservices should use Event Sourcing & CQRSHugh McKee · Voxxed Days Microservices 2019
• 01h 07mAn Architecture with CQRS and Event SourcingEugen Paraschiv · Voxxed Days Bucharest 2016
• 40m7 Reasons why your microservices should use Event Sourcing & CQRSHugh McKee · Voxxed Days Cluj-Napoca 2019
• 51mMicroservices Data Patterns: CQRS & Event SourcingEdson Yanaga · Devoxx Belgium 2017
• 46mMicroservices Data Patterns: CQRS & Event SourcingEdson Yanaga · Voxxed Days Bucharest 2018
• 55m7 Reasons why your microservices should use Event Sourcing & CQRSHugh McKee · Riga Dev Days 2019
• 48mNodeJS Microservices + CQRS + Event Sourcing — Why Do I Do This?Roman Sachenko · JS Fest 2018