PouchDB uses the exact same replication API as CouchDB, its fairly simple (although not so much to implement) Conflicts (when the data has been modified on bot

PouchDB uses the exact same replication API as CouchDB, its fairly simple (although not so much to implement) Conflicts (when the data has been modified on both sides independantly) are simple dealt with by storing both versions of the document, the app author can then choose one, or merge to create a new document to fix the conflict. http://guide.couchdb.org/draft/conflicts.html http://guide.couchdb.org/draft/conflicts.html - has some more information It is a hard problem, you have to deal with offline edits + conflicts, minimizing the amount of changes that are transferred, Hopefully this is useful for people dealing with those problems so they dont need to start from scratch