title: How to avoid Zuul becoming a bottleneck
body: <p>I'm working on a microservice architecture with Ribbon/Eureka/Hystrix and Zuul, everything is working fine. But as we're working with microservices, we can scale our microservices as we want and have different instances of the same µservice. For now, load balancing is working great with one instance of Zuul, different Eureka instances made as cluster and different instances of µservices. The question is: can I define more than one instance of Zuul? If yes, doesn't Zuul can be accessed using different ports and is losing the reverse-proxy role that's making its strength? 'cause for now, I see it as a single point of failure and a potential bottleneck.</p>
  
  <p><strong>Can someone please explain how to avoid this problem?</strong></p>