On Sep 26, 2015, at 5:07 PM, Brendan Duddridge <[email protected]<mailto:[email protected]>> wrote:
Isn't handling all of that what enabling continuous replication does for you? Yeah, but you’d have to have a continuous pull replication running with every peer on the network, for as long as that peer was online. And a continuous pull keeps a TCP socket open as long as it’s active. That’s potentially a lot of TCP connections. Instead, I’m handling the notification of new sequences/revisions using TXT records, which are much lighter weight — they’re multicast IP packets. There’s still going to be a “thundering herd effect<https://en.wikipedia.org/wiki/Thundering_herd_problem>” when someone updates a document, as everyone else simultaneously starts a replication and pulls the new revision. There are ways around that, but they require more sophisticated protocols like gossip or spanning trees. —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/A31ABCB2-42BA-4A1D-964C-90A38874B5D0%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
