Implementing Event-driven Microservices
summary
Covers concrete choices and tradeoffs: uses domain‑driven design to pick service boundaries, advocates event sourcing + CQRS for eventual consistency, and explains sagas and compensating actions with an orchestration-over-choreography recommendation. Mentions Kafka and cloud message‑bus options, snapshotting to avoid replay cost, and failure scenarios (partial commits, rollbacks, visibility). Expect practical patterns, code‑level implications, and operational caveats rather than high‑level rhetoric.
AI-written summary · about
chapters (31)
- 0:00Intro
- 0:14Agenda (2/2)
- 0:50Monolithic: The old school approach ...
- 1:49Microservices: The Brave new world...
- 4:59Loose Coupling → Distributed Data
- 6:48How to create service boundaries?
- 8:58DDD: Aggregates
- 10:13Data Partition Strategies. Use DDD
- 12:27Problems with Distributed Data
- 13:12Cannot use ACID Transactions
- 13:50Cannot use 2-Phase Commit
- 14:44Eventual Consistency
- 17:34Event Driven Architecture
- 19:11Communication: Direct Messaging
- 22:06Communication: Via Message broker
- 23:11Communication Patterns
- 24:41Event Sourcing: Introduction
- 27:15Event Sourcing: Snapshots
- 28:12Event Sourcing: Multiple views
- 29:00Event Sourcing: Benefits & Drawbacks
- 29:31Command Query Responsibility Segregation
- 30:46CORS: Benefits & Drawbacks
- 31:15Sagas: Introduction
- 32:27Transaction & Rollback Transaction
- 33:40Sagas: Example
- 35:29Sagas: No Isolation!
- 38:25How to sequence the transactions?
- 39:24Choreography: Benefits & Drawbacks
- 40:10Orchestration : Benefits
- 41:40Resources
- 43:36Summary
related talks
47mEvent-Driven Microservices = Microservices Done Right
51mPatterns & Practices of Implementing Event-driven MicroSvc...
42mCreating event-driven microservices: the why, how and what
01h 25mBuilding microservices with event sourcing and CQRS
56mDeveloping Event-driven Microservices w/Event Sourcing and CQRS
27mBuilding Microservices Architecture The Right Way based on Saga Pattern
01h 11mEmbracing Messaging and Eventual Consistency in your Microservices Solutions
44mEvent-Driven Microservices, the Sense, the Non-sense and a Way Forward
