spring cloud - Scaling out the zuul proxy -


we have scaled out sevices in our system having more 1 instance of them registered in eureka service registry.

also, proxied zuul server in front.

my question how can ensure scalability of zuul proxy when accessed clients.

one solution can think of having multiple instances of proxy registered in eureka registry. if done how decide on of instances exposed clients.

we faced same issue in our application, having multiple instances of multiple types of micro-service-type applications on our backend. servers registered eureka. problem had multiple security gateways configured (based on architecture described in excellent tutorial: https://spring.io/guides/tutorials/spring-security-and-angular-js/).

eventually decided use hardware http load balancer calls our security gateways in round-robin approach (our solution on-prem).

we use redis @enablehttpredissession annotation have spring session synced across servers, http load balancer not have deal sticky sessions or stateful considerations. round-robin security gateways. doesn't matter if load balancer hits sg1, sg2 or sg3, share same session information coming redis (which configured fail-over redis sentinel).


Comments

Popular posts from this blog

java - Run spring boot application error: Cannot instantiate interface org.springframework.context.ApplicationListener -

python - pip wont install .WHL files -

Excel VBA "Microsoft Windows Common Controls 6.0 (SP6)" Location Changes -