domain driven design - Strategy to introduce CQRS in classic CRUD system -
i'm looking way migrate cqrs driven architecture running anaemic model/transaction script'ish system. thinking of making current state (handcrafted) snapshot event sourcing pick further changes. proper way it?
yes, 1 way it. used special xxximported
event current state make import event explicit (even though xxximported
not part of domain language).
we found it's idea conversion gradually, , start use cases can see benefits of using cqrs+es, i.e., can actual performance gains, can achieve looser coupling or can benefit explicit event history. trivial use cases, or cases performance doesn't matter, can converted later.
Comments
Post a Comment