Re: Collaboration using Event Sourcing
Freddy Hansen <[email protected]>
| Newsgroups | gmane.comp.programming.domain-driven-design |
|---|---|
| Message-ID | <CADqkBqiW-hA8BitbPC_CtbWA2bbaWqvcWFDuE-yY1fmCDgfCKw@mail.gmail.com> |
I would suggest you solve the synchronization issues in the business domain (not the database). That way you can e.g. have 2 updates on the same row at the same time without conflict. I think it was in one of Udi Dahans old podcasts where he talks about this kind of problems. Freddy Hansen Senior Consultant Amende AS On Oct 8, 2013 7:22 AM, "Tom Eugelink" <[email protected]> wrote: > ** > > > On 2013-10-08 07:18, Tom Eugelink wrote: > > > > > You can sync each client copy with a master and thus everything become > eventually consistent. > > > Buzz word misuse detected! Each database is of course consistent on its > own (anyone not using foreign keys and other constraints should receive > physical punishment). This is not Cassandra, I should have used the word > "synchronized". > > Tom > >