CODEWITHSUNDEEP
domain-driven-designcqrsevent-sourcing
Pepster
Pepster

Reputation: 2166

Strategy to introduce CQRS in classic CRUD system

I'm looking for a way to migrate to a CQRS driven architecture from an already running anaemic model/Transaction Script'ish system. I was thinking of making the current state a (handcrafted) Snapshot from where Event Sourcing will pick up further changes. Would this be a proper way to do it?

Upvotes: 0

Views: 150

Answers (1)

Alexander Langer
Alexander Langer

Reputation: 2893

Yes, that is one way to do it. We used a special XXXImported event with the current state to make the import event explicit (even though XXXImported is clearly not part of the domain language).

We found it's a good idea to do the conversion gradually, and start with those use cases where you can see benefits of using CQRS+ES, i.e., where you can get actual performance gains, can achieve looser coupling or where you can benefit from explicit event history. Trivial use cases, or cases where performance doesn't matter, can be converted later.

Upvotes: 3

Related Questions