Microservice Architecture Based on Event Sourcing

on YouTube ↗26m

" summary

A bookshop example shows replacing UI-backend calls with an event bus (Kafka, RabbitMQ, ActiveMQ) so services no longer need addresses, gain plug‑and‑play, and pull work at their own pace; responsibility for actions like shipping moves to the service that listens for a BookOrdered event. Queries remain hardest: shared DB is an anti‑pattern, remote query recreates tight coupling and latency, and event-carried state transfer duplicates data and forces eventual consistency. Recommendation: choose remote query for large, rare datasets, replicate for small/fast data, and expect tradeoffs.

AI-written summary · about

" chapters (9)

1. 0:00Introduction and setup
2. 1:03Event sourcing basics
3. 2:05Request-driven microservices issues
4. 5:58Event-driven microservices benefits
5. 9:51Event vs command vs query
6. 12:21Query challenges and solutions
7. 18:31Event-carried state transfer
8. 22:11Choosing the right approach
9. 23:16Q&A session

" related talks

• 46mMicroservices Data Patterns: CQRS & Event SourcingEdson Yanaga · Voxxed Days Bucharest 2018
• 51mMicroservices Data Patterns: CQRS & Event SourcingEdson Yanaga · Devoxx Belgium 2017
• 58mImplementing Event-driven MicroservicesNikhil Barthwal · DevOpsCon Spring 2019
• 47mEvent-Driven Microservices = Microservices Done RightUrs Peter · J-Fall 2022
• 51mPatterns & Practices of Implementing Event-driven MicroSvc...Nikhil Barthwal · GeeCON Prague 2023
• 01h 25mBuilding microservices with event sourcing and CQRSMichael Ploed · SpringOne2GX 2015
• 44mUnlocking Business Agility with Event-Driven ArchitecturesOskar Neumann, Dirk Fröhner · AWS Summit Berlin 2023
• 56mDeveloping Event-driven Microservices w/Event Sourcing and CQRSChris Richardson · Philly ETE 2015