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

I build an internal project using CouchDB2 as a backend in 2017 and it's still used today. CouchDB definitely surpassed my expectations in what has been possible to do with it. Its biggest advantages are that data sync is effortless and that it uses HTTP as a protocol, so you can communicate directly with it from a web application.

Used it this school year for a research project that needs solid replication of content and a firehose of updates. There are dozens of such projects but nothing beats the simplicity and versatility of basic HTTP calls with JSON documents and the robustness of a 15-years old project that Just Works.

Was some time ago (2016), but we built and released Typeform LITE (form creator via text-entry-like interface for smartphones) with CouchDB + PouchDB which was a pleasure as far as I can remember. Was really neat to get local-first functionality almost out of the box with web tech on smartphones.

We are using it internally as just a document store (with some erlang views but that is it). It scales very nicely, but for smaller documents postgres does the job for us so we are (slowly) moving away to simplify the tech stack.

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.

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

I'm using it as a database for my application, SolarThing: http://github.com/wildmountainfarms/solarthing

I was naive when I chose it (I was just starting to program then), but it has served me well. It's replication feature is simple to setup and is robust. It uses a REST API for any calls to the database, and it is a well designed API. I don't use all its features, but I really like it for the ones I use.

I have built advertisement bidders and ad servers. I avoid querying the database on every request (and caches) by creating app in-memory materialized views of the database. See https://www.confluent.io/blog/leveraging-power-database-unbu... for more about this. Another cool feature of the replication protocol is that I can tell if all app servers are on the same version of the data.

We are still using couchdb for user profile synchronisations. Basically user details and data from mobile synched to the cloud. In our application users do not interact between one another. So basically we use db per user model. This gives us synchronisation between mobile/web clients. Pity that there is no up to date mobile library for couchDB and we depend on an old one.

We used 1.6 for a large project in 2014 or so, the 2.x release removed key features for us and we were never able to upgrade. The direction they went after that just never really worked for us so we only have that legacy project still running.

It is still being used by a cool open-source project, Kazoo, which is essentially a multi-tenant PBX.

I was wondering the same thing

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 and a cloud) much more like git uses push & pull. No other database really puts that into an open source / open government project.

There’s tons more cool stuff that CouchDB does and its being used in mission critical infrastructure that you’re relying on every day :)

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 was about. The one reason it was created is replication and simplistic conflict handling, and it does it perfectly.

The reason CouchDB never took off is that it targets offline-first, something you'll see associated with peer-to-peer systems, but does that only for servers: you're supposed to install that thing through packages, configure a text file, run it with your preferred daemon manager, ... If CouchDB had a simple desktop version you could start in one click and forget about, it would have been way more interesting. Alas.

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

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

Well, npm did... https://github.com/npm/npm-registry-couchapp

Unless you are IBM.

fixed, thanks

They also have QuickJS as an option in this release.

it _supports_ one for a specific legacy users, the default is more modern.