2 ms·
I'm the original author. Any application built following the CQRS/ES pattern requires development of the same building blocks: command registration and dispatch
by slashdotdash 10y ago
I'm the original author. Any application built following the CQRS/ES pattern requires development of the same building blocks: command registration and dispatch; hosting and delegation to aggregate roots; event handling; long running process managers.
I built Commanded as a self-contained, reusable, open-source library. With the goal of demonstrating one approach to implementing the pattern using Elixir. I hope it provides some use. That's why I've written up the case study. Anyone can take the code as is, to bootstrap their own application. Use it as a learning tool, take away the good ideas. Rebuild and improve upon the bad.
I received a pull request only today adding support for Greg Young's event store. That's going to broaden the appeal.
- itsthecourier 10y agoSounds great. By the way, in a common CRUD app with an entity having 30 fields, you basically: used a DTO, modified its data and merged in the DB row. Are we supposed to create 30 CQRS commands for this? Like property1updated, property2updated, etc.?