CQRS with Erlang

on YouTube ↗36m

" summary

Connects the CQRS and Event Sourcing architectural patterns (separating command/write and query/read stores, modeling state as events) with Erlang’s strengths for building concurrent, distributed systems. Presents a sample Erlang implementation showing how Erlang’s concurrency, distribution, and fault-tolerance map to CQRS concerns (scaling read/write stores independently, handling event streams and concurrency) and contrasts where implementing CQRS in languages like C# or Java becomes difficult.

AI-written summary · about

" chapters (9)

1. 0:00Start
2. 3:10Domain Driven Design
3. 7:01Task-based UI
4. 11:59keep your privates private
5. 15:22explicit & tunable staleness
6. 15:49Let the business tweak CAP
7. 16:02simplify conflicts, read- write contention, and concurrency
8. 18:29Erlang (the Language)
9. 19:19Erlang (The VM)

" related talks

• 51mCQRS + ES = CRUD, QEDValentin Kasas, Damien Gouyette · Scala.IO 2016
• 47mFrom C to Q, One Event at a Time: Event Sourcing in PicturesLorenzo Nicora · Voxxed Days Ticino 2017
• 17m7 Reasons why your microservices should use Event Sourcing & CQRSHugh McKee · Voxxed Days Microservices 2019
• 30mEventSourcing and CQRS — The Introduction That Was MissingSławomir Jachowicz · JDD 2017
• 04mCommand Query Responsibility SegregationOlivier Loverde · dotJS 2018
• 55m7 Reasons why your microservices should use Event Sourcing & CQRSHugh McKee · Riga Dev Days 2019
• 01h 25mBuilding microservices with event sourcing and CQRSMichael Ploed · SpringOne2GX 2015
• 51mMicroservices Data Patterns: CQRS & Event SourcingEdson Yanaga · Devoxx Belgium 2017