Re:Why Replication is Awesome
by rdtsc on Thursday November 07, 2013 @02:17PM
(#6691727)
That is true but the conflict is preserved in the database. So a change feed set up to monitor conflicts will notice it immediately. You do have to set up the monitor and conflict resolver.
From the CAP standpoint your system is available but not consistent for a short period of time because initially on a GET during a conflicted document you might get one version but after the custom merge resolve runs, it could end up replacing with another.
That is the price to pay for availability, and it works best if applications on top are designed to work with it. It is not always possible so this, so it is a tool that is good in some cases but not in all cases.
From the CAP standpoint your system is available but not consistent for a short period of time because initially on a GET during a conflicted document you might get one version but after the custom merge resolve runs, it could end up replacing with another.
That is the price to pay for availability, and it works best if applications on top are designed to work with it. It is not always possible so this, so it is a tool that is good in some cases but not in all cases.