3 ms·

CouchDB's killer feature (not mentioned on the linked page) is of course, offline replication. So you can take a copy of the database with you, work in disconne

by jchrisa 16y ago

CouchDB's killer feature (not mentioned on the linked page) is of course, offline replication. So you can take a copy of the database with you, work in disconnected mode, and synchronize later. And this can be done with any number of users, all writing and synchronizing independently.

richardhenry 16y ago
People keep mentioning this. What are some real-world uses for this feature? Who is using CouchDB in this fashion, and what are they doing with it?
- shpxnvz 16y ago
  One example of CouchDB offline replication: http://one.ubuntu.com/ http://one.ubuntu.com/
- jchrisa 16y ago
  Here's a CouchApp that (with a non-demo dataset) we use internally for TODO management. I have a copy running on my laptop, on my MacMini at home, on the office server, in the cloud, and of course, on my Android phone. I synchronize them when I feel like it (but I could configure it to continuously synchronize in the background). http://couchapp.couchone.com/focus/_design/focus/index.html#/focus http://couchapp.couchone.com/focus/_design/focus/index.html#... For more info on the method of serving HTML5 apps directly from CouchDB's web-server: http://couchapp.org/page/what-is-couchapp http://couchapp.org/page/what-is-couchapp
qwzybug 16y ago
Of course, data synchronization is never automagic—the dirty little secret of all distributed systems. Merging is hard!
- jchrisa 16y ago
  In CouchDB's document model this manifests itself as the challenge of of deciding how to split the results of user interactions across documents. Eg: don't store comments on the blog post document, keep them on their own documents, as they have different update patters. Of course this pattern doesn't answer everything, but it gets the vast middle of use cases.