Moxi & Reverse Proxy
I am testing Couchbase for Memcached use to see if we can use it for our application.
To keep all code simple, I prefer to use a local client moxy, so all code contains 'localhost'.
Since the amount of servers we use will be growing, I don't want to keep adding servers to the moxi config.
The Couchbase documentation says:
The "Gold Standard" best practice (if you have the flexibility) is to put the Couchbase host URLs behind a http reverse-proxy, so that all the client-side Moxi's can be more easily configured with a "stable" URL which can handle cluster changes without having to touch each client-side Moxi like..
Does this mean, I have to cofigure the moxi with 2 (failover) 'stable' ip's on which a server runs that outputs the couchbase servers?
What must be the output of the rev proxies?
Thanks for your advice.
Thank you for your reply.
I was aware that it is not required, however, we are expecting a sudden and exponential growth.
To keep it manageble we would like to use the reverse proxy option, but I haven't found any instructions as to how this must be done.
Any reverse proxy of your choice is okay. You'll just want to be sure that it support HTTP chunked (sometimes called HTTP streaming) connections for long periods of time. You will be able to handle the sudden growth in either case, as momentary outages of moxi (usually less than a second) don't often cause serious issues so you can add more URIs to the list for moxi if need be.
Thanks again for taking the time to respond.
Are there any details what the reverse proxy must output?
I haven't fount example configs yet.
This is not required. You can simply run moxi with multiple IP addresses in it's configuration. The reverse proxy is merely a way to keep from having to restart many moxis if your cluster topology changes. Instead, you'd update your configuration only at the reverse proxy.