CouchDB

35 engineers on Hacker News describe using CouchDB first-hand: 12 endorse it, 4 regret it, 7 are mixed.

66%trust
35first-hand users
30in production
endorse 12mixed 7regret 4uses, no opinion

“I've used CouchDB and PouchDB on a previous project, and it was a blast... My only regret is the limited support (at the time) for full text search and complex queries.”

mixed · production · dSebastien · 2021-10-26 · source ↗ · wrong label?

“I have a CouchDB in prod that throws an error message about connection limit a few times a day. ... It restarts the docker container to recover”

mixed · production · shane_b · 2021-10-26 · source ↗ · wrong label?

“Syncing was a solved problem in the CouchDB world, so we moved to CouchDB. ... I really hope CouchDB could bring in some ACL management”

mixed · production · karmelapple · 2020-06-07 · source ↗ · wrong label?

“It is my go-to solution but I'm unaware of problems at scale.”

endorse · personal · fareesh · 2016-12-23 · source ↗ · wrong label?

“CouchDB 2.0 is still rough around the edges, particularly with its new Fauxton interface. CouchDB 2.0 brings the _bulk_get API which has improved sync by an order of magnitude(s).”

mixed · production · hardcopy · 2016-12-05 · source ↗ · wrong label?

“I'm a big fan of CouchDb, Pouch, and CBL, all of which my team uses.”

endorse · production · karmelapple · 2016-12-05 · source ↗ · wrong label?

“moving out of Cloudant and into CouchDB with an openresty based reverse proxy has made things even better”

endorse · production · azr89 · 2016-12-05 · source ↗ · wrong label?

“Getting the same entity simply from CouchDB yields response times of 3ms.”

endorse · production · naranha · 2016-12-02 · source ↗ · wrong label?

“Tested, deployed in production and after a while we figured out that most of the promises about performance, stability, etc we're mostly bull.”

regret · production · luka-birsa · 2016-05-24 · source ↗ · wrong label?

“CouchDB is actually my favorite "I just wanna hack something" database for the above reasons.”

endorse · personal · gecko · 2016-01-29 · source ↗ · wrong label?

“We use it in production, and we're slowly migrating some data out of SQL into CouchDB. It's very stable, operates over an HTTP API”

endorse · production · mikegioia · 2015-07-30 · source ↗ · wrong label?

“I've been using a lot of CouchDB for my current project... what I like about Couch is how it forces me to create the correct indexes and therefore be fast.”

endorse · personal · m_mueller · 2013-11-11 · source ↗ · wrong label?

“I've been using CouchDB (and now BigCouch) for about four years and it's both clever and useful. ... The only downside is that adding a view with trillions of rows can take quite a while.”

mixed · production · 4 yr · smoyer · 2013-11-10 · source ↗ · wrong label?

“Having used Couchdb in production for two years, I have to agree with his analysis, and offer my own opinion that Couchdb is highly overrated.”

regret · production · 2 yr · tony_landis · 2013-11-07 · source ↗ · wrong label?

“the team I was leading decided that CouchDB would be a good fit... the overheads of utilising CouchDB massively outweighed the ever-shrinking benefit.”

regret · production · scott_w · 2012-12-20 · source ↗ · wrong label?

“we also use a number of other great technologies like CouchDB (specifically BigCouch), RabbitMQ, OpenSIPS”

endorse · production · josh2600 · 2012-07-10 · source ↗ · wrong label?

“Our dataset in Couch is 28 million records, takes up 13GB of data”

endorse · production · mark242 · 2012-06-01 · source ↗ · wrong label?

“I've been using CouchDB for a long time with a lot of apps and instances”

endorse · production · cemerick · 2011-11-01 · source ↗ · wrong label?

“I put together a similar logging setup for our servers... I'm using CouchDB for my store... Biggest drawback... is that it loves to devour disk space”

mixed · production · ConstantineXVI · 2011-10-14 · source ↗ · wrong label?

“We experimented with couch replication but quickly went back to running separate (beefy) chef-servers”

regret · production · moe · 2011-10-09 · source ↗ · wrong label?

“The ride with CouchDB has been bumpy at times, but not at the 'scale' where linkfluence is at.”

mixed · production · tillk · 2011-03-08 · source ↗ · wrong label?

“they seem to have ironed out the nagging dependency issues couch had displayed on debian-based installations and are now reliably passing all of the unit / end-to-end tests.”

endorse · production · rosenbergdm · 2010-07-15 · source ↗ · wrong label?

“We've been using CouchDB in production for at least six months with our web-based content management system and our mobile advertising platform.”

endorse · production · 0.5 yr · inc · 2010-07-14 · source ↗ · wrong label?

“I made a version that runs offline. The user has to install CouchDB on their desktop pc to use it.”

neutral · personal · oblib · 2022-12-19 · source ↗ · wrong label?

“because CouchDB _id indexes are lexicographic, meaning I more often than not can just use the main index”

neutral · personal · WorldMaker · 2017-11-30 · source ↗ · wrong label?

“We're still running Couch 1.6. We have yet to evaluate Couch 2.0.”

neutral · production · 1.25 yr · ojanik · 2016-12-05 · source ↗ · wrong label?

“sync to a CouchDB 2.0 database in Digital Ocean.”

neutral · production · PaulMest · 2016-12-04 · source ↗ · wrong label?

“Lastly a tiny process that archives a final roll-up of data past 48 hours (currently) to CouchDB”

neutral · production · vidarh · 2014-12-12 · source ↗ · wrong label?

“For long term storage, we migrate rolled up data to couchdb at the moment”

neutral · production · vidarh · 2014-10-10 · source ↗ · wrong label?

“the multi-tenancy and RBAC system remained in Ruby and on CouchDB... A big push for 12 was moving this into Erlang and Postgres.”

neutral · production · mmzyk · 2014-09-08 · source ↗ · wrong label?

“So we ditched the cluster-thingie and moved everything to CouchDB. Pricy hardware, but the saved man-hours recouped that within a month or two.”

neutral · production · msiebuhr · 2014-07-15 · source ↗ · wrong label?

“I've got CouchDB in production on two systems, but for applications or portions of applications that are well-suited to a document-store.”

neutral · production · smoyer · 2013-11-12 · source ↗ · wrong label?

“but CouchDB for the metadata and the results of our algorithms.”

neutral · production · dem · 2011-11-23 · source ↗ · wrong label?

“I've been using MongoDB for well over a year now in around 6 apps (moved on from CouchDB)”

neutral · production · matthewcford · 2011-11-07 · source ↗ · wrong label?

“was a factor in picking CouchDB over others”

neutral · production · rdtsc · 2011-11-01 · source ↗ · wrong label?