If a smart client is not available for your chosen platform, the
alternative option is to deploy a standalone proxy, which
provides the same functionality as the smart client, while
memcached compatible interface
layer locally. A standalone proxy deployed on a client may also
be able to provide valuable services, such as connection
pooling. The diagram below shows the flow with a standalone
proxy installed on the application server.
The memcached client is configured to have just one server in
its server list (localhost), so all operations are forwarded to
localhost:11211 — a port serviced by
the proxy. The proxy hashes the document ID to a vBucket, looks
up the host server in the vBucket table, and then sends the
operation to the appropriate couchbase server on port 11210.