Hacker News Reader

Comment by grizzles | Hacker News Reader

Is the project sponsored by Couchbase? If not, have you thought about publishing a storage API that the replication protocol calls so that it could be adapted to work with any backend db? What about P2P sync - (eg. serverless) has anyone thought of making PouchDB do that?

View on HN

Not sponsored by Couchbase at all (I worked at Couchbase during its formation, this started near the end of my time there).

For pluggable storage engines our node.js adapter uses leveldown, so any *down backend can be plugged in. https://pouchdb.com/adapters.html has some more information about this.

For p2p yup its been something quite a few people have been using pouchdb for, one of the more notable examples has been http://thaliproject.org/, the core storage format is entirely compatible with p2p (inherited from couchdb)

AFAIK, Couchbase is a CouchDB as a service tuned for speed.

PouchDB is a CouchDB implementation in the browser. I don't think your sync with other db would be easy and I believe there is no such desire in the project roadmap.

No, Couchbase is more or less a merge of Membase and Couchdb. With Couchdb it only shares its lineage and its creator; apart from that they are entirely different beasts.

It also shares more than half its name. The recognisable bit. The other bit is the generic and largely interchangeable "base" / "db". I don't know if it's intentional, but there's no wonder people get them confused.

The idea of making pouch sync with other databases is covered in their faq:

https://pouchdb.com/faq.html#sync_non_couchdb

Basically, your other data base probably handles conflicts in a different way to Couch that would make syncing this way nonsensical.

If you're happy to handle that yourself, the Couch replication protocol is well documented and there are plenty of libraries written for it.

Reply on news.ycombinator.com