About memcached in couchbase

Couchbase Server
1

I see that Couchbase Server includes a memcached service as one of its components. My question is about compatibility:

  • Is the memcached service running inside Couchbase the same software as the official memcached community project (from memcached.org), or is it Couchbase’s own implementation?

  • Does it use the same binary protocol and commands as the official memcached server?

  • If I have an application that already talks to a standard memcached server, can I point it to Couchbase’s memcached service and expect it to work without modification?

I’d like to know whether Couchbase’s memcached service is a drop-in replacement for a standalone memcached deployment, or if there are limitations / differences I should be aware of.

Thanks in advance for the clarification!

2
  • If I have an application that already talks to a standard memcached server, can I point it to Couchbase’s memcached service and expect it to work without modification?

I suppose you could try it.

The protocol is described here - kv_engine/docs/BinaryProtocol.md at master · couchbase/kv_engine · GitHub

3

Hi @zeus64 , the simple answer is no, you can’t connect an application that speaks memcached to Couchbase Server.

We forked memcached a long time ago, and while we used to have a way to connect memcached clients (a component called “Moxi”, which could be run client-side or server-side), we discontinued that some time ago now (around Server 5.0 time, IIRC).

You’ll have to update your application to use one of our SDKs instead.

4

But there’s already a service called memcached.exe running and listening on port 11211 (the default memcached port). Do you mean that’s we can’t connect directly to this port?

5

@zeus64 The process is still called memcached, yes. Which version are you running?

6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.