Niclas wrote:
> It is a long time ago. But I think I was thinking a lot about how Greg
> Young explained how he does persistence only with an EventStore.
>
> From that should follow that events should be delayed until
> complete(), yet be visible within the UoW thread.
>
> It could also be that I would like to see a more advanced Event system
> in general, which can be used for all kinds of things, not only
> storage. (Think ZeroMQ) And in that, there are also some transactional
> aspects that should be considered, similar to how hazelcast
> updates/events are delayed until commit.
Understood, very interesting topic.
> It is a large and fairly complex matter, so I am not sure we should
> engage in it with so little resources available. I suggest to move it
> out of 2.0 scope.
I moved the issue to 2.1 for now.
We'll see if we put some effort into the existing eventsourcing library
before going the full EventStore path later.
/Paul
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
