CouchBase mixed with Memcached, loss of most CouchDB philosophies and functionality?

Question

As of now, the only way i have worked with newer versions of CouchBase, is through a memcached Client. I use Erlang as the

Answer 1

The relationship between Couchbase and CouchDB is covered in detail here: http://www.couchbase.com/couchdb

In short, Couchbase is aimed at the main NoSQL use-case: big data that must be available for end-user interaction. Things like session storage for ad-targeting, game data storage for fast growing social games. Or anywhere user demands can grow unexpectedly.

Couchbase is horizontally scalable, CouchDB is not. To get the scalability and speed Couchbase offers, we've hat to cut back some of the features people like in CouchDB. It's a different set of tradeoffs, but the common denominator is the JSON and the map reduce index model.