Live data from Hacker News

CouchDB 3.4.1 Released

blog.couchdb.org

31–40 of 47 posts

Re: CouchDB 3.4.1 Released

#31
post #28
post #10

Earlier quoted context omitted.

CouchDB dev here. While that was our idea early on for a while, we have loooong (10+ years) moved away from this narrative. CouchDB is a document database that can be essentially indefinitely clustered to grow and shrink with your application / traffic demands. It also comes with a unique replication protocol that allows you to synchronise casually connected instances (say offices around the world, or mobile devices…

> ...replication protocol that allows you to synchronise casually connected instances... That single featurte right there was why i first had started playing with couchDB several years ago. It really had been quite awesome! I think other features that help it really help with offline-first approaches also are really cool! But, ultimately, after playing with it (and really liking it), i just didn't have a need for too…

No offence taken, SQLite is great technology :) — My company makes a (commercial) CouchDB add-on based on SQLite to add SQL queries to CouchDB (link provided for informational purposes): https://neighbourhood.ie/products-and-services/structured-qu...

Re: CouchDB 3.4.1 Released

#32
post #7
post #2

Curious to hear who is using it still. I experimented with it 2010/2011 IIRC but never build a real project with it.

We tried to use it alongside pouchdb to provide offline first experience. We ran into a lot of issues, mainly with pouchdb bugs. Then after reading this list [1] of issues in the couchdb architecture we decided to ditch it and stop trying to make pouchdb work. [1] https://news.ycombinator.com/item?id=17115649

Out of curiosity, if you would like to start a new, offline-first project that needs syncing, which database would be the best candidate today?

Re: CouchDB 3.4.1 Released

#33
post #7

Earlier quoted context omitted.

We tried to use it alongside pouchdb to provide offline first experience. We ran into a lot of issues, mainly with pouchdb bugs. Then after reading this list [1] of issues in the couchdb architecture we decided to ditch it and stop trying to make pouchdb work. [1] https://news.ycombinator.com/item?id=17115649

Out of curiosity, if you would like to start a new, offline-first project that needs syncing, which database would be the best candidate today?

I would still recommend you give CouchDB and PouchDB a fair shot. They are used successfully by many folks.

Re: CouchDB 3.4.1 Released

#34
post #7

Earlier quoted context omitted.

We tried to use it alongside pouchdb to provide offline first experience. We ran into a lot of issues, mainly with pouchdb bugs. Then after reading this list [1] of issues in the couchdb architecture we decided to ditch it and stop trying to make pouchdb work. [1] https://news.ycombinator.com/item?id=17115649

Out of curiosity, if you would like to start a new, offline-first project that needs syncing, which database would be the best candidate today?

One interesting idea I’ve seen is none[1]. That’s definitely more on the exploration side than the shipping one, though.

[1] https://tonsky.me/blog/crdt-filesync/

Re: CouchDB 3.4.1 Released

#37

Earlier quoted context omitted.

Out of curiosity, if you would like to start a new, offline-first project that needs syncing, which database would be the best candidate today?

One interesting idea I’ve seen is none[1]. That’s definitely more on the exploration side than the shipping one, though. [1] https://tonsky.me/blog/crdt-filesync/

hum, allow me to toot my own horn here. I've written something to that effect in 2021. https://raphael.lullis.net/thinking-heads-are-not-in-the-clo...

Re: CouchDB 3.4.1 Released

#38
post #6
post #5

CouchDB was always a curious product that asked the question, "what would happen if your database and your application server were the same product?" Unfortunately I think the answer was nobody would use it.

Unless you are IBM.

Not sure whether this is a Lotus Notes reference also, but it should be! (that's where the idea for CouchDB came from)

Re: CouchDB 3.4.1 Released

#39
post #2

Curious to hear who is using it still. I experimented with it 2010/2011 IIRC but never build a real project with it.

I tried to build some hobby stuff with it (mostly worked), planning to use it instead of mongodb @work but I got hit by the limitations of the JS engine version used at the time and it got frustrating too fast for a small hobbyist project. The mongodb/couchdb thing at work was cancelled so I didn't spend more time with it.

People behind it are really, really nice though.

One of the top (the top I think ?) obsidian sync plugin uses it.

Re: CouchDB 3.4.1 Released

#40
post #7

Earlier quoted context omitted.

We tried to use it alongside pouchdb to provide offline first experience. We ran into a lot of issues, mainly with pouchdb bugs. Then after reading this list [1] of issues in the couchdb architecture we decided to ditch it and stop trying to make pouchdb work. [1] https://news.ycombinator.com/item?id=17115649

Out of curiosity, if you would like to start a new, offline-first project that needs syncing, which database would be the best candidate today?

I am (very) biased but Couchbase has a pretty solid Mobile offering for native apps. I have worked on the Sync Gateway component responsible for replication for the last six years.

Sync Gateway still maintains a CouchDB-compatible REST API, and PouchDB _mostly_ works thanks to that, but there are some corner cases and features that PouchDB does not support so YMMV with it. Our native app libraries have used a more performant websocket-based replication protocol for many, many years now, and I'd really love to have the time investigating a PouchDB adapter using this WS protocol instead.

Post reply on HN