The Future of Apache CouchDB • Hacker News Board

Re: The Future of Apache CouchDB

#11

Post by perezd » Thu, Jan 05, 2012, 9:48 PM UTC

sktrdie wrote: post #7

nestlequ1k wrote: post #5

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

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.

Re: The Future of Apache CouchDB

#12

Post by mark_l_watson » Thu, Jan 05, 2012, 10:06 PM UTC

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.

Re: The Future of Apache CouchDB

#13

Post by mark_l_watson » Thu, Jan 05, 2012, 10:12 PM UTC

nestlequ1k wrote: post #5

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

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.

Re: The Future of Apache CouchDB

#14

Post by mlmilleratmit » Thu, Jan 05, 2012, 11:10 PM UTC

sktrdie wrote: post #7

nestlequ1k wrote: post #5

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

I agree. This is getting overly complicated.

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.

Re: The Future of Apache CouchDB

#15

Post by dieswaytoofast » Fri, Jan 06, 2012, 1:18 AM UTC

There are two issues be-deviling couchDB as it stood before, well, now - * front-end caching * back-end scaling. The back-end scaling is handled quite wonderfully by BigCouch (we're users, and pretty damn happy ons at that), but pretty much everybody rolls their own for front-end caching (lord knows, we did, with mnesia, and a bunch-o other erlang. My hope had always been that we would end up with some version of BigCouchBase, but that is clearly not going to happen. With Adam's post, the back-end-scaling issue is pretty much a 'taken care of' issue as far as CouchDB is concerned.

Thanx Adam (and everyone else at Cloudant!)

Re: The Future of Apache CouchDB

#16

Post by smacktoward » Fri, Jan 06, 2012, 4:16 AM UTC

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

Re: The Future of Apache CouchDB

#17

Post by re_todd » Fri, Jan 06, 2012, 6:29 AM UTC

sktrdie wrote: post #7

nestlequ1k wrote: post #5

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

I agree. This is getting overly complicated.

Yeah, this makes me want to learn MongoDB instead.

Re: The Future of Apache CouchDB

#18

Post by js4all » Fri, Jan 06, 2012, 7:50 AM UTC

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.

Re: The Future of Apache CouchDB

#19

Post by janl » Fri, Jan 06, 2012, 8:57 AM UTC

smacktoward wrote: post #16

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

Re: The Future of Apache CouchDB

#20

Post by Shamanmuni » Fri, Jan 06, 2012, 4:49 PM UTC

smacktoward wrote: post #16

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

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.