Event tracking

13 views
Skip to first unread message

Jan Van Ryswyck

unread,
Apr 21, 2010, 3:45:57 PM4/21/10
to DDDD Review/Discussion
The document on "Events as a Storage Mechanism" contains the following
paragraph:

"In a system that is Domain Event centric, the aggregates are
themselves tracking strong events as to what has changed within them.
There is no complex process for comparing to another copy of a graph,
one would simply ask the aggregate for its changes. The operation to
ask for changes is far more efficient than having to figure out what
has changed."

I was chatting with Mark Nijhof the other day on this very topic and
he talked about refactoring his sample application to let the UOW
track the events instead of the aggregates themselves. Is this a
better approach?


PS: I really liked the content of these documents and I'm looking
forward to read more :-).


--
Subscription settings: http://groups.google.com/group/DDDDReviewDiscussion/subscribe?hl=en

Greg Young

unread,
Apr 21, 2010, 4:24:35 PM4/21/10
to ddddreview...@googlegroups.com, DDDD Review/Discussion
Btw this is in book accidentally sent first reply just to you will
forward to the group

Sent from my iPhone

On Apr 21, 2010, at 9:45 PM, Jan Van Ryswyck

Greg Young

unread,
Apr 21, 2010, 4:23:50 PM4/21/10
to ddddreview...@googlegroups.com
Yeah I was showing mark that refactor the last time I was in Bergen.
It's an ok concept but keep in mind you should only ever be using 1 ar
at a time in a pure sense (no consistency between). Some event stores
may support it but it causes problems in distributed stores

Sent from my iPhone

On Apr 21, 2010, at 9:45 PM, Jan Van Ryswyck
<jan.van...@gmail.com> wrote:

Reply all
Reply to author
Forward
0 new messages