On Fri, Jun 1, 2012 at 10:07 PM, Paul Merlin <[email protected]> wrote: >> * Event Store model. > If I understand correctly this means that EventSourcing would be built > in Qi4j persistence support. In other words, we would gain EventSourcing > "for free". Am I right?
Event Sourcing (I think) is a larger scope, since this will only deal with CRUD and Event Sourcing utilizes the richer domain model. So, the primitives needed to build Event Sourcing should be part of Qi4j Core, and Qi4j itself only has an "CRUD domain model", so that part is ES... Makes sense? >> * Transition events in store. > > I see TimeSeries coming :) Yes, once the transitions are captured, history and timeseries data on properties becomes fairly straight forward. >> * Asynch model for store/retrieve. > > Would it mean that underlying stores "transactions" (or whatever it > is) should be done in a separate thread? It means that it is possible. Doesn't mean we need to implement it straight away. >> Finally, is this too much of a change for 2.0, and should be scheduled >> for a 3.0 right away?? *I* think this is the right way to go, and I >> think some areas in the persistence system will be simplified, as well >> as setting the stage for "historic data" support, stronger >> distribution capabilities, event sourcing model and much more... > > I wouldn't bother scheduling this for 2.0, it depends on the amount of work > it is. On one hand it could delay 2.0 and impact motivation but on the other > hand theses changes are really interesting and would break compatibility so > they can't be in a 2.x release. I have no strong opinion on this yet but I > have the gut feeling that it will have impacts that need discussion (what > about query?, migration? etc..). Correct. I think you are spot on... It feels "too big" for 2.0, yet I think it is important enough to bring it up... Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/6a2pl4j I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
