We have used Couchbase Server in our product. Its an Intranet application whose front end is pure JavaScript. We however use Erlang/OTP for the Business Logic, authentication (Mnesia), yaws web server and a bunch of other erlang libraries.
Now, we are still using the Couch Base Single Server whose download has been removed from the Couch base site. We have found it very stable. In now, 5 months of running live, it has never gone down. We are running it on top of Ubuntu Server. So, our interest in NoSQL is just beginning.
However, as i asked a question and another here about Erlang Client support for Couch base server, i discovered that they say:
Couchbase Server is memcached compatible. This means many existing memcachedSo i then started looking around for these memcached compatible libraries and have found a bunch of them: at Google code, Erlang Mc,erlmc, mcache, memcached-client and finally OneCached By Process One (Makers of Ejjabberd XMPP Server). With my great aim (if possible), of implementing my own client for Couch Base server 1.8 and 2.0 , the question follows:
client libraries and in many cases, the applications already using these
libraries, may be used directly with Couchbase Server
1 . Which of the above memcached Erlang Client libraries is appropriate for use with Couchbase 1.8 and 2.0 ?
2. If it is compatible, can i directly use it, or i have to make some changes first ? please do explain the changes ?
3. Is anyone out there feeling the need for Erlang Client support for Couch Base server 2.0 and 1.8 as we do ? How are they working their way around this problem ?
I would appreciate it, if a Couch Base
insider having membership here on stackoverflow, do tell us if Couch base team has plans of building us an Erlang Client possibly in any near future so that we do not waste our time attempting so, as they are in position of building a much better and efficient client to their own server, than we can. Thanks to all
