Hacker News new | ask | show | jobs
by daleharvey 4614 days ago
I mostly agree, CouchDB's data and query model only works well for a subset of use cases and anything past that subset (the line at which is vague and only really understandable after being burnt) makes life hard. I do think that the query model and general capabilities can (and will) be vastly improved, but its already taken too long.

However I dont agree that many (or any) other things are suitable alternatives for replicatable json stores, in this case where replication means peer to peer stores that can operate offline for any period of time.

My particular interest these days is building web applications that work well offline, its why I build PouchDB, while its entirely possible to build a home made sync solution on top of your favourite database, its an extremely hard problem and something I see app after app try and fail constantly.

If I didnt need the ability sync data that would work offline, I wouldnt use CouchDB (pouchdb/cloudant etc), but since that is what I am interested in, right now I think its pretty much the only choice.

1 comments

I think the kind of thing you are doing is the sweet spot for couch. Perhaps over time it will be less so, but I now I think it is pretty unique.