Why not use the community edition of couchbase?
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.
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).
The way we treat JSON is similar but the performance characteristics are radically different.
and the replication model
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.
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.
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.