I used PouchDB w/ CouchDB as the datastore for a digital wallet. Used to store ZKs for proof of age etc.
Worked a treat
Offline-First with CouchDB and PouchDB in 2025
11–20 of 25 posts
Re: Offline-First with CouchDB and PouchDB in 2025
#12PouchDB and CouchDB were what inspired me to build Triplit[1]. The idea of having an identical (or merely similar in the case of Pouch/Couch) query engine accessible on client and server is insanely powerful. The author links to a much longer post on handling conflicts which is worthy of its length because it's not a pleasant experience with this setup. I highly recommend trying a modern setup from one of the many ne…
Great to see the founder of Triplit here! PouchDB was definitely ahead of its time, and it’s exciting to see its legacy being carried forward by so many modern local-first (lo-fi) solutions. I’ve also been a longtime fan of Triplit - its API, docs, and overall DX (plus direct community interaction) are excellent. Also Triplit's universal client/server model means you never have to care about all the complexity of oth…
Please let's not make lo-fi mean local-first.
Re: Offline-First with CouchDB and PouchDB in 2025
#13[dead]
Re: Offline-First with CouchDB and PouchDB in 2025
#14PouchDB and CouchDB were what inspired me to build Triplit[1]. The idea of having an identical (or merely similar in the case of Pouch/Couch) query engine accessible on client and server is insanely powerful. The author links to a much longer post on handling conflicts which is worthy of its length because it's not a pleasant experience with this setup. I highly recommend trying a modern setup from one of the many ne…
Nice, I’ll have to try out Triplit. There’s also Couchbase which has a local sync database in C++ IIRC. Also, heads up the first triplit link I tried gave me a 404: https://www.triplit.dev/docs/client/query/select#selecting-r...
Great catch, fixed!
Re: Offline-First with CouchDB and PouchDB in 2025
#15PouchDB and CouchDB were what inspired me to build Triplit[1]. The idea of having an identical (or merely similar in the case of Pouch/Couch) query engine accessible on client and server is insanely powerful. The author links to a much longer post on handling conflicts which is worthy of its length because it's not a pleasant experience with this setup. I highly recommend trying a modern setup from one of the many ne…
triplit sounds awesome. Any precedence of someone using it from a native iOS app?
With React Native yes but not yet with Swift. There's been quite a few requests to my surprise through--I figured CloudKit, etc would be sufficient on iOS but I don't have experience there.
Re: Offline-First with CouchDB and PouchDB in 2025
#16I would love to see a sync solution that didn't want to replace my datastore, or mediate all access to it.
This approach means the tools have to be good at not just sync, but also querying, business logic, validation, authn, authz, trigger background jobs, etc. That's a lot!
I'm not trying to eliminate my backend, nor an all-in-one frontend DB. I've tried tools that do that, and I've come to think the approach has severe limits.
I wonder if there's not a way to offer a two-way stream of data change events, with conflict detection/resolution, which I can process with my own code.
Re: Offline-First with CouchDB and PouchDB in 2025
#17I had quite the offline-firat déjà vu, when I saw local-first trending the last two years.
Re: Offline-First with CouchDB and PouchDB in 2025
#18PouchDB and CouchDB were what inspired me to build Triplit[1]. The idea of having an identical (or merely similar in the case of Pouch/Couch) query engine accessible on client and server is insanely powerful. The author links to a much longer post on handling conflicts which is worthy of its length because it's not a pleasant experience with this setup. I highly recommend trying a modern setup from one of the many ne…
Is Triplit overkill (over PouchDB) if multi-user collaboration is not a use case?
Re: Offline-First with CouchDB and PouchDB in 2025
#19PouchDB and CouchDB were what inspired me to build Triplit[1]. The idea of having an identical (or merely similar in the case of Pouch/Couch) query engine accessible on client and server is insanely powerful. The author links to a much longer post on handling conflicts which is worthy of its length because it's not a pleasant experience with this setup. I highly recommend trying a modern setup from one of the many ne…
Nice, I’ll have to try out Triplit. There’s also Couchbase which has a local sync database in C++ IIRC. Also, heads up the first triplit link I tried gave me a 404: https://www.triplit.dev/docs/client/query/select#selecting-r...
Couchbase had a lot of subtle incompatibilities with PouchDB in my attempts to use it on a past project. The big one I recall was that Couchbase had far more restrictions on key names and that required some workarounds.
(Though to be fair Apache has been threatening to shrink the key space greatly as well with the considered move to the Foundation-based "CouchDB 4.0".)
Re: Offline-First with CouchDB and PouchDB in 2025
#20PouchDB and CouchDB were what inspired me to build Triplit[1]. The idea of having an identical (or merely similar in the case of Pouch/Couch) query engine accessible on client and server is insanely powerful. The author links to a much longer post on handling conflicts which is worthy of its length because it's not a pleasant experience with this setup. I highly recommend trying a modern setup from one of the many ne…
Great to see the founder of Triplit here! PouchDB was definitely ahead of its time, and it’s exciting to see its legacy being carried forward by so many modern local-first (lo-fi) solutions. I’ve also been a longtime fan of Triplit - its API, docs, and overall DX (plus direct community interaction) are excellent. Also Triplit's universal client/server model means you never have to care about all the complexity of oth…
[dead]