You may also choose to run moxi on the "client-side". That means installing and running moxi, for example, on your web-application server hosts.
This has the advantage of increased performance, especially for PHP-style applications that use occasional process restart strategies. (Think of classic CGI apps in the worst case.) Since a client-side moxi server can run on the same machine as the memcached client application (usually a web host), the memcached client only needs to make a fast local machine network connection to moxi, the client-side moxi server can reuse long-running connections (saving on TCP connection setup handshake time), and the client-side moxi can multiplex multiple clients into shared connections (reducing the file descriptor usage on the servers.)
Additionally, client-side moxi's can provide some simplified configuration benefits. The client applications can connect to the client-side moxi, which might be running at "127.0.0.1:11211" instead of having the manage their own server-lists and having to have their own code to handle cluster reconfigurations. The client-side moxi can participate in the same dynamic cluster reconfiguration algorithms of Couchbase. Any cluster membership or health changes can propagate automatically to the client-side moxi's instances.
See Chapter 3, Standalone Moxi Component for more information about configuring a client-side moxi.