I had quite the offline-firat déjà vu, when I saw local-first trending the last two years.
PouchDB 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 new local first solutions [2]
I 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.
I used PouchDB w/ CouchDB as the datastore for a digital wallet. Used to store ZKs for proof of age etc.
Worked a treat
> Vite, well, it’s in the name. Fast build tooling.
Can someone explain this to me? I’m clearly missing something about its name.
[dead]
CouchDB - is JD Vance a power user?