> Now, why would two updates in 0.5 seconds considered conflict? Why would > conflict result in huge delay?
It’s not a conflict causing the delay & warning; it’s a missing update notification from the database server. Andy on the Sync Gateway team has been investigating the cause of missing sequences, and re-implementing some of the code to track sequences more robustly. This tends to happen more often on a highly loaded database server. > sometimes updating it will take 4 to 10 seconds, which is not acceptable. We do intend to figure out and fix this glitch, but Couchbase Mobile is not intended to be a real-time system, so that sort of latency can occur. > The votingsession doc, on the other hand, will be frequetly updated (2 times > per seconds), because all related-users are voting in one voting session > (therefore each user can see who has already voted, and who has not). I don’t know the details of your application, but having one document that’s frequently updated by multiple users is usually not a good design, because it’s very prone to conflicts. In general it’s better for each user to have their own document that they update; then you can use a query to group together the related documents and produce the aggregated result. —Jens -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/1AA2154A-FFB7-41F6-8537-9A67DB26F51B%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
