I have done some further probing. It seems Couchbase Single Server is
same product tree as the CouchDb and hence there is compatibility on
the APIs. However the CouchBase Server as such uses the memcached-
based proxy layer in between, which cannot be accessed through
couchrest API but by couchbase-ruby-client API.
There are several advantages which can be seen using the couchbase
server rather than the underlying couchdb server (or couchbase single
server), like having a integrated memcached layer as well as being
able to span across multiple servers in seamless manner.
The catch here is that anything stored directly on couchdb server (say
using couchrest APi) will not be visible through the couchbase layer,
as that brings in concept of vbuckets.
Thus there seem to be compatibility issue which seem to be cropping
in. Is there a possibility of porting the couchrest_model onto the
couchbase server, basing it on couchbase-ruby-client API from
original couchrest API. Should be possible, and would allow users of
couchrest_model to move easily to the couchbase server. I am
particularly fond of the ORM layer which Counchrest_model provides. It
might start with forking the couchrest_model and making it more
acceptable on the underlying API layer (couchrest vs couchbase-ruby-
What are your thoughts on how difficult it might be. What would be a
good starting point? Or is this even the way to go?
It may be encroaching on your efforts, but do you have any plans for
this. Maybe community as such could help.
I am no expert on this, unlike you, so please correct my
interpretation of the issue. Any help in getting forward with it would
On Aug 25, 2:31 pm, Samuel Lown <sam.l...@gmail.com
> Hi Sameer,
> Should be fine. I use CouchRest with Couchbase Server with no problems. I'm
> not sure it'll be officially supported at the moment, but given that
> Couchbase releases are always based on an official and stable CouchDB API I
> can't foresee any issues. The same could also be said for Cloudant.
> Having said that, if you spot any issues, let us know!