Have you thought about using a shared file system for the cache. This way all the nginx 's are looking at the same cached content.
On Jul 7, 2017 5:30 AM, Joan Tomàs i Buliart <joan.to...@marfeel.com> wrote: Hi Lucas On 07/07/17 12:12, Lucas Rolff wrote: > Instead of doing round robin load balancing why not do a URI based > load balancing? Then you ensure your cached file is only present on a > single machine behind the load balancer. Yes, we considered this option but it forces us to deploy and maintain another layer (LB+NG+AppServer). All cloud providers have round robin load balancers out-of-the-box but no one provides URI based load balancer. Moreover, in our scenario, our webservers layer is quite dynamic due to scaling up/down. Best, Joan _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx This message is confidential to Prodea unless otherwise indicated or apparent from its nature. This message is directed to the intended recipient only, who may be readily determined by the sender of this message and its contents. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient:(a)any dissemination or copying of this message is strictly prohibited; and(b)immediately notify the sender by return message and destroy any copies of this message in any form(electronic, paper or otherwise) that you have.The delivery of this message and its information is neither intended to be nor constitutes a disclosure or waiver of any trade secrets, intellectual property, attorney work product, or attorney-client communications. The authority of the individual sending this message to legally bind Prodea is neither apparent nor implied,and must be independently verified.
_______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
