> On Jun 13, 2015, at 2:09 PM, Brendan Duddridge <[email protected]> wrote: > > Is this robust enough for lots and lots of data syncing? That is, if I import > 1000 records while offline, then plug into the mesh, will all the devices in > the mesh get all the changes? And if I had made changes on the other devices > will that also get merged into the new device that just joined the mesh?
Yes, it has correct behavior. The underlying replication architecture (inherited from CouchDB) is multi-master and supports arbitrary topologies. It does the right thing even if there are redundant connections and/or devices leave and rejoin. This kind of mesh isn’t super scalable, though. I go into that a bit during the talk. Everyone syncs with everyone else, which leads to O(n^2) traffic on the LAN. The implementation optimizes that a bit by not re-advertising changes that arrive from peers, so any document update should lead to only O(n) replications. A more scalable approach would probably use something like a dynamic spanning tree, which creates the minimal number of connections that connect all the peers, but those are more difficult to implement. —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/7C2ADF3C-70A4-4942-A7A3-958EEC7D3D9B%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
