Developing Event-driven Microservices w/Event Sourcing and CQRS

on YouTube ↗56m

" summary

Explains an implementation: each aggregate persists a sequence of business events, not a current row, and the system persist events instead of state then replays them (with periodic snapshots) to reconstruct state; the event store doubles as the publish/subscribe source so services consume events—sometimes a “four‑or‑five event” ping‑pong completes a money transfer—and CQRS moves reads to materialized query views (ElasticSearch, MongoDB, DynamoDB) updated asynchronously for fast joins.

AI-written summary · about

" chapters (39)

1. 0:00Intro
2. 2:17Traditional application architecture
3. 4:35Obstacle to frequent deployments
4. 4:50Overloads your IDE and container
5. 5:31Obstacle to scaling development
6. 6:05Requires long-term commitment to a technology stack
7. 6:33Limitations of a single relational database
8. 7:30Apply the scale cube
9. 8:04Use a microservice architecture
10. 8:30Use NoSQL databases
11. 8:59Different modules use different types of databases
12. 10:17Update two entities in a NoSQL database
13. 10:35Cassandra main table index table
14. 11:30Event-based architecture to the rescue
15. 12:35Eventually consistent money transfer transfer Money
16. 13:48Update and publish using 2PC
17. 14:18Use data store as message queue
18. 16:40Persists events NOT current state
19. 17:18Replay events to recreate state
20. 20:34Event store implementations
21. 21:09Optimizing using snapshots
22. 22:12Aggregate traits
23. 23:10Account - command processing
24. 25:31Aggregate type classes/implicits
25. 26:35Business benefits of event
26. 28:47Technical benefits of event
27. 29:41Drawbacks of event sourcing
28. 33:28Strategic design: identify sub- domains
29. 33:57Strategic design: define microservices
30. 34:17Decide inter-service communication mechanisms
31. 36:17Use the familiar building blocks of DDD
32. 36:48Designing domain events
33. 38:00The anatomy of a microservice
34. 38:51Asynchronous Spring MVC controller
35. 40:09Handling events published by Accounts
36. 41:52Command Query Responsibility Segregation (CQRS)
37. 42:50Query-side microservices
38. 44:44Benefits and drawbacks of
39. 47:23Summary

" related talks

• 01h 25mBuilding microservices with event sourcing and CQRSMichael Ploed · SpringOne2GX 2015
• 17m7 Reasons why your microservices should use Event Sourcing & CQRSHugh McKee · Voxxed Days Microservices 2019
• 55m7 Reasons why your microservices should use Event Sourcing & CQRSHugh McKee · Riga Dev Days 2019
• 46mMicroservices Data Patterns: CQRS & Event SourcingEdson Yanaga · Voxxed Days Bucharest 2018
• 40m7 Reasons why your microservices should use Event Sourcing & CQRSHugh McKee · Voxxed Days Cluj-Napoca 2019
• 47mFrom C to Q, One Event at a Time: Event Sourcing in PicturesLorenzo Nicora · Voxxed Days Ticino 2017
• 51mMicroservices Data Patterns: CQRS & Event SourcingEdson Yanaga · Devoxx Belgium 2017
• 47mEvent-Driven Microservices = Microservices Done RightUrs Peter · J-Fall 2022