The Future of Apache CouchDB | Hacker News Reader

The Future of Apache CouchDB

blog.cloudant.com

137 pointsjashkenas18 comments

It felt a bit unfair that someone who hasn't contributed to a project in more than a year, declared it obsolete and urged everyone to move on (even if they were the original founder).

Also the choice of Couchbase to use "Couch" in their product name while completely breaking API compatibility between Couchbase Server and Apache CouchDB is a sly move.

All that left a bad taste in mouth. Good to see someone from Cloudant responded.

This is where actual innovation is happening. I'm not at all discouraged by the FUD being perpetuated by Katz today. I have a fairly modest BigCouch deployment in production and I am very happy with it. haters gonna hate.

I have built and experimented with BigCouch several times (but never in production except for using Cloudant's hosted service). BigCouch is a nice project. Anyway, this is good news, and I thought that this blog post showed some class (i.e., nicely written, polite, etc.)

For the first time, I did build Couchbase from source today (I didn't realize that it was open source until today), and the web UI is slick, and the official Ruby client worked fine. That said, I found the experience confusing because the Couchbase client page has a lot of CouchDB clients listed, and even though I know that the interface is different, I tried a few of them anyway - didn't work.

Seems majorly confusing, and will potentially divide the community. Couchbase vs CouchDB. Can anyone explain the difference?

Couchbase 2.0 is Membase Server (http://www.couchbase.com/products-and-services/membase-serve...) merged with CouchDB, and as I understand it, Couchbase 2.0 more closely resembles Membase Server at the moment (http://www.couchbase.org/get/couchbase/2.0.0).

I agree. This is getting overly complicated.

Its not that complex. CouchDB is the core technology that Couchbase and BigCouch, et. al are using to power their more "vertical" offerings, in various degrees. CouchDB is not going anywhere, and its a great standalone product.

We're certainly hoping to reduce the complication by removing the boundary between (clustered) BigCouch and Apache CouchDB by making the clustering an optional and transparent part of the Apache CouchDB project.

Yeah, this makes me want to learn MongoDB instead.

potentially divide the community. Couchbase vs CouchDB

Actually that would be a step up from the current situation, which is "Apache CouchDB" vs "BigCouch" vs "CouchBase".

I view CouchDB and BigCouch to be very similar since the client APIs and libraries are the same, so both have the same developer experience. Couchbase uses different client libraries and doesn't seem to have the language coverage that CouchDB and BigCouch do.

All three are open source and you can build them yourself.

For me Damien's announcement to abandon CouchDB landed like a bomb. CouchDB is one of the key technologies of our hosting service. It is a great to see one of the big players (Cloudant) to step in.

It makes me happy to see this.

Previous discussion: http://news.ycombinator.com/item?id=3427491

amen.

> Working with the ASF and the CouchDB community, we hope to integrate the core capabilities of BigCouch into Apache CouchDB. Hopefully this will put to rest the tired (and false) “CouchDB doesn’t scale” meme.

This is kind of hilarious, seeing as how the whole reason why CouchDB (and all the other NoSQL databases) exist is because of the "MySQL doesn't scale" meme...

> This is kind of hilarious, seeing as how the whole reason why CouchDB (and all the other NoSQL databases) exist is because of the "MySQL doesn't scale" meme...

It is also not true.

Wrong, the whole reason why NoSQL databases exist is that SQL databases aren't always the best solution for any given problem. CouchDB in particular tries to solve different problems than MySQL does, or the same problems in a different way. You should learn about it rather than citing misinformed memes.

Reply on news.ycombinator.com