11–20 of 47 posts
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.
Curious to hear who is using it still. I experimented with it 2010/2011 IIRC but never build a real project with it.
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.
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.
Well, npm did... https://github.com/npm/npm-registry-couchapp
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.
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.
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…
Curious to hear who is using it still. I experimented with it 2010/2011 IIRC but never build a real project with it.
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…
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
Curious to hear who is using it still. I experimented with it 2010/2011 IIRC but never build a real project with it.
Curious to hear who is using it still. I experimented with it 2010/2011 IIRC but never build a real project with it.