[maverwa]

I tried coming up with EventSourcing attempts for a large application that’s basically only shuffling around data from n source systems to m target systems (sometime of them are both). I thought ES would be perfect, as we mostly care about changes and where to they came from, not so much about the current state (mostly…) But I am not smart enough. I just could not come up with a way to make it work. I do not understand the darn thing, even after spending hours reading fowlers and others stuff. The basics sound simple enough to me. Store events, not state, generate state from history of events. But does each event belong to one entity, to one type of entities, or is it global? We have a quite elaborate net of things interconnected and reliant on other, changed and provided via vastly different services/protocols/etc.

I think I need some more braincells to understand Event Sourcing.

[dwmcc]

> does each event belong to one entity, to one type of entities, or is it global

Are you asking about building aggregates in CQRS? Or is this specific to event sourcing?

Were your concerns were with modeling your domain more so than the infrastructure powering the "event sourcing"?