News for hackers. Stuff that matters.
Re:CouchDB merges in BigCouch by gecko on Thursday July 25, 2013 @04:08PM (#6104642)
I think CouchDB is vastly underrated as a hacker database for toy projects. We're talking about an incredibly simple database, with powerful replication abilities, with brain-dead administration, and one-click offsite backup and synchronization, that requires no real client libraries to work with. It makes it comically easy for me to hack on toy projects on the road, then sync them right back up afterwards when I'm done.

I know CouchDB sometimes gets some flak for not performing as well as other NoSQLs. Anecdotally, that feels as if it's gotten a lot better over time, and this BigCouch merge may improve things further, but sometimes there's a case to be made for using something just because it's fun and easy to work with.

Re:CouchDB merges in BigCouch by batgaijin on Thursday July 25, 2013 @04:56PM (#6104916)
Why not use the community edition of couchbase?
Re:CouchDB merges in BigCouch by rdtsc on Thursday July 25, 2013 @10:29PM (#6106251)
Here is why:

* No _changes feed. (TAPs won't do here sorry). I mean that is uber killer feature of CouchDB. Otherwise, just pick any other key value store.

* HTTP interface to DB : you can use CouchDB to store both your data and your code. That is very cool.

* Futon : that is the web based db and document browser and viewer. That is killer. Being able to see what is in your database and debug before that data is used by some other part of the system is invaluable.

Re:CouchDB merges in BigCouch by garrensmith on Friday July 26, 2013 @04:55AM (#6107230)
We working on a new version of Futon. Adding a ton more features. Will be out later this year.
Re:CouchDB merges in BigCouch by Lazare on Thursday July 25, 2013 @05:19PM (#6105065)
The only thing Couchbase has in common with CouchDB is the name, and some of the same people are involved. If you like CouchDB, there's no particular reason you'd like Couchbase (and visa versa).
Re:CouchDB merges in BigCouch by jchrisa on Friday July 26, 2013 @03:24AM (#6107017)
The way we treat JSON is similar but the performance characteristics are radically different.
Re:CouchDB merges in BigCouch by janl on Friday July 26, 2013 @04:26AM (#6107178)
and the replication model
Re:CouchDB merges in BigCouch by Argorak on Thursday July 25, 2013 @05:05PM (#6104975)
Because Couchbase has very different features and an almost completely different interface. For example, there is no changes stream, etc.

The name lies a bit.

Re:CouchDB merges in BigCouch by lackbeard on Thursday July 25, 2013 @07:42PM (#6105686)
It's a horrible name.
Re:CouchDB merges in BigCouch by daleharvey on Thursday July 25, 2013 @05:15PM (#6105042)
I worked on both databases, they have entirely different advantages / disadvantages and use cases, none of the OP really apply to couchbase.
Re:CouchDB merges in BigCouch by rubiquity on Thursday July 25, 2013 @05:09PM (#6104999)
Big difference for me is that Couchbase doesn't have an HTTP interface. That is one of my absolute favorite features of CouchDB (along with master-master replication and the changes stream).