We used Couchbase Server in our product. This is an Intranet application, the front of which is pure JavaScript. However, we use Erlang / OTP for business logic, authentication ( Mnesia ), the yaws web server and many other erlang libraries.
Now we are still using the Couch Base Single Server , the download of which has been removed from the Couch base site . We found it very stable. At present, after 5 months of running, he has never fallen. We run it on top of Ubuntu Server. So, our interest in NoSQL is just beginning.
However, since I also asked here about Erlang Client support for the Couch base server, I found that they say:
Couchbase Server is memcached compatible . This means many existing memcached
client libraries and in many cases, the applications already using these
libraries, may be used directly with Couchbase Server
So I started looking for these
memcached compatible libraries and found a bunch of them: at
Google code ,
Erlang Mc ,
erlmc ,
mcache ,
memcached-client and finally
OneCached By Process One (Ejjabberd XMPP Server Manufacturers) . With my big goal (if possible), to implement my own client for Couch Base Server 1.8 and 2.0, the question is:
1. Which of the above Erlang memcached client libraries is suitable for use with Couchbase 1.8 and 2.0?2. If it is compatible, can I use it directly, or do I need to make some changes first? please explain the changes?3. Does anyone out there feel the need for Erlang customer support for Couch Base 2.0 and 1.8, just like us? How do they deal with this problem?I would appreciate if the Couch Base
insider had a membership here in stackoverflow, tell us if the Couch base team has plans to build us Erlang client, perhaps in the near future so that we donβt waste time on it, since they able to create a much better and more effective client on our own server than we can.
Thank you all
source share