Live data from Hacker News

CouchDB 3.4.1 Released

blog.couchdb.org

21–30 of 47 posts

Re: CouchDB 3.4.1 Released

#21
post #17
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…

> There’s tons more cool stuff that CouchDB does and its being used in mission critical infrastructure that you’re relying on every day :) If you could share a bit on those I think the community would be extremely interested. There was that CERN thing a decade ago, if it's still true or there are other actors with similar amounts of data, there would be fewer comments about not finding CouchDB useful

Yeah we are working on that. Sometimes it is hard to get public info out of private projects, but there’s going to be a bit more on that in the not so distant future :)

Re: CouchDB 3.4.1 Released

#23
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.

I think that better describes zodb/hope. Or gemstone glass.

https://zodb.org/en/latest/tutorial.html

Re: CouchDB 3.4.1 Released

#24
post #14
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.

Map/Reduce was a hype of the days it was created, but you're perfectly fine not using it. CouchDB has been integrating MongoDB-style queries for a few releases now, and this very release introduces a full-text search engine. Map/Reduce is still there because it just works. The real shame is that Map/Reduce is simply a toy, easy-to-add bonus when looking at the data structure, but that's not what CouchDB is or ever wa…

There are client implementations, such as PouchDB for the browser and Couchbase Lite (community edition) for mobile platforms.

Re: CouchDB 3.4.1 Released

#25
In the release notes highlights:

> Optionally replace md5 with xxHash for data integrity checksums. 30% speed up on larger (128k) docs, no difference for smaller docs.

Happy to see xxHash getting more and more popular!

Re: CouchDB 3.4.1 Released

#27
I think there’s a small oversight in the release notes:

> In that case, upgrade to 3.4.0 without changing the default and enable xxHash in 3.5.0 or later so you can roll back to 3.4.0 then.

This should probably say 3.4.1, not 3.4.0, in the two places in that sentence where it says 3.4.0. Right?

Re: CouchDB 3.4.1 Released

#28
post #10
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.

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 many personal use-cases....since sqlite was "good enough". I thought - and still believe - that for wider (maybe corporate/enterprise?) uses, it can still fit the need....but i don;t hear much buzzz about it in general...so in my case, i stopped using it, and forgot about it. Apologies to any devs behind it, no offnese meant...i just got my personal use-cases covered by sqlite...and on enterprise side, too many internal politics to convince stakeholders that couchdb would be better than other solutions in some use cases.

Also, the documentation back in the day to get started was ok-ish, but there didn't seem to be much around....i guess it could be one of those things where it is/was a great thing...but if not enough attention and use exists, then it won;t trigger a wider audience of devs who will also document more stuff and further triugger a virtuous cycle?

Anyway, good to see the devs are still at it! :-)

Re: CouchDB 3.4.1 Released

#29

I think there’s a small oversight in the release notes: > In that case, upgrade to 3.4.0 without changing the default and enable xxHash in 3.5.0 or later so you can roll back to 3.4.0 then. This should probably say 3.4.1, not 3.4.0, in the two places in that sentence where it says 3.4.0. Right?

fixed, thanks

Re: CouchDB 3.4.1 Released

#30
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 still use couchdb & pouchdb only for syncing data for our salesmen app.

It's an offline first PWA (Salesman need to make an order even if offline).

And pouchdb make it easier because we don't have to care about indexeddb, leveldb or whatever of users browser's db.

So its a single codebase for serving web, ios and android.

Its great for sync but less then good for other uses

Post reply on HN