Domain Driven Design with CQRS and Event Sourcing

Domain Driven Design, CQRS and Event Sourcing presentation made during Node.js Paris meetup (https://www.meetup.com/fr-FR/Nodejs-Paris/events/263358579/)

Transcript

2. ❤
5. ! if(this.authProvider.validate(token)) { this.service .send(session.get("user_basket")); }
6. • ⚠ • • ℹ • •
8. • • • • • • • • •
9. !=
10. Actor Behavior Aggregate Event View Command
11. Actor Behavior Aggregate Event Command
15. • • • • • • ⚠
16. CQRS GetBalance Query Deposite Command GetAllOperation Query Withdraw Command … … Dispatcher Read DB Dispatcher QueryHandler CommandHandler Write DB Validation Plugin Monitoring Plugin Cache Plugin … ⚠ Eventual consistency
18. • What is Event Sourcing? • Capture all domain changes as a sequence of events (stream) • Every changes in the domain are represented by events • Events are immutable • Event Store will be the single point of truth • Useful for: • Auditing • Debug • Fix inconsistency • Description of the pattern by Martin Fowler: https://martinfowler.com/eaaDev/EventSourcing.html Event Sourcing
19. • • • • • • • • • • • •
20. CQRS & Event Sourcing GetBalance Query Deposite Command GetAllOperation Query Withdraw Command … … Dispatcher Read DB Dispatcher QueryHandler CommandHandler Event Store Projection Projection Aggregate State Events Behaviors
22. • • • • • • • • • • • •
24. ☺