Re: Collaboration using Event Sourcing
Joseph Flood <[email protected]>
| Newsgroups | gmane.comp.programming.domain-driven-design |
|---|---|
| Message-ID | <CAOg4kjGMb5HR_ZrOZXK-Ld2_Pb=oxa2kQ_1eT0Yb2pSMpL9t0Q@mail.gmail.com> |
I believe Greg covers these kind of systems in his online course. Check out the video titled - "Occasionally Connected Systems" - http://subscriptions.viddler.com/GregYoung On Sat, Sep 21, 2013 at 10:35 PM, Ashley at Metamaxim < [email protected]> wrote: > ** > > > Hi > > I am not sure that I totally understand the scenario you are considering, > but it seems to me that you should consider Service Choreography ( > http://en.wikipedia.org/wiki/Service_choreography) as an approach. > > Choreography is a technique for designing stateful collaborations where > participants interact by asynchronous messaging over a network. In > particular, it is concerned with how you ensure by design that the final > state of the participants is consistent. > > Regards > Ashley > > > > On 20/09/2013 22:55, [email protected] wrote: > > > > I have a business domain where a team of people will go somewhere and > collaborate together with fat clients over a local network and possibly a > remote network. They will also sometimes be offline. I envision a rich > domain with events and the use of event streaming. Events would occur > locally per client and then need to be published. The subscribers would > need to process the events as an idempotent operation. The clients need to > be eventually consistent. Can an asynchronous event publish/subscribe > model work here? Does it make sense? I would think some sort of callback > would be in order so that events are not continuously sent over and over > with the use of some sort of projection snapshot? > > > >