NodeJS Microservices + CQRS + Event Sourcing — Why Do I Do This?

on YouTube ↗48m

" summary

Describes building Node.js microservices using CQRS and Event Sourcing to produce a replayable audit log for debugging and dispute resolution. Implementation combines Kafka streams, MongoDB snapshots and Winston logging to deliver replayable events for reproducing bugs at scale, while noting operational costs and tradeoffs like duplicated models, library failures, missing Kafka topics, eventual-consistency delays, and the need for deployment and automated topic-creation scripts plus a service template to make it work.

AI-written summary · about

" chapters (9)

1. 0:00Introduction
2. 1:40CQRS and Event Sourcing
3. 8:47Event Sourcing basics
4. 15:57Event Sourcing in practice
5. 20:49Event Sourcing challenges
6. 25:45Logging in event-driven
7. 28:16When Event Sourcing fails
8. 31:48Implementation tips
9. 35:28Q&A

" 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
• 46mMicroservices Data Patterns: CQRS & Event SourcingEdson Yanaga · Voxxed Days Bucharest 2018
• 56mDeveloping Event-driven Microservices w/Event Sourcing and CQRSChris Richardson · Philly ETE 2015
• 55m7 Reasons why your microservices should use Event Sourcing & CQRSHugh McKee · Riga Dev Days 2019
• 58mImplementing Event-driven MicroservicesNikhil Barthwal · DevOpsCon Spring 2019
• 40m7 Reasons why your microservices should use Event Sourcing & CQRSHugh McKee · Voxxed Days Cluj-Napoca 2019
• 40mClean Microservices Communications with CQRS and Event SourcingOliver Sturm · Øredev 2024