Front End

All external systems that send requests to CUE Zipline send them to its web service endpoint. Any request sent to a particular CUE Zipline instance's endpoint will be processed on that instance. In order to distribute the load between multiple CUE Zipline instances, therefore, the requests must be actually directed to those specific instances. The easiest way to do this is to enable load balancing in the reverse proxy that you should already be using to handle TLS termination for CUE Zipline (see Proxying CUE Zipline).

graphics/load-balanced-zipline.png

With the reverse proxy handling load balancing, it is then only necessary to specify the proxy as the CUE Zipline endpoint when configuring external client systems (that is, CUE Print, drop resolvers and the CUE editor).