search

ibm-cloud-architecture / refarch-cloudnative-netflix

Reference application for deploying microservice-based applications onto IBM Bluemix, leveraging the Netflix OSS framework.
26 stars 16 forks source link

Scaling out #20

Open kiransahoo opened 7 years ago

kiransahoo commented 7 years ago

How is scaling out handled for each of these microservices for e.g entree microservice ? Don't see any reference or explanation of that in the reference architecture. Please advise. Thanks

jesusmah commented 7 years ago

Hi @kiransahoo, we did not have enough time to further develop this architecture so there were things we had to unfortunately left out such as how to scale the app out. However, you could have a look at the Auto-scaling service we have available in IBM Bluemix (https://console.ng.bluemix.net/docs/services/Auto-Scaling/index.html). As far as maintaining SLA of an architecture, you should also bear in mind Cloud Service Management and Operation. I would encourage you to look at (https://www.ibm.com/devops/method/content/architecture/serviceManagementArchitecture)

kiransahoo commented 7 years ago

Thanks @jesusmah for the response. The link mentioned don't talk about the load balancer software once the microservice is scaled out. Do we have any reference document for that ? For e.g if IBM uses netflix ribbon as the load balancer or any other techniques once the microservices are scaled out. Appreciate your immediate response. It would greatly help us moving our application to IBM cloud.

jesusmah commented 7 years ago

In our architecture we use the Zuul proxy component of the Netflix OSS. In particular we are using the Embedded Zuul Reverse Proxy you can read about in (http://cloud.spring.io/spring-cloud-static/spring-cloud-netflix/1.2.0.M1/). This proxy implements Ribbon so that all requests will be load balanced among all instances of the service registered with eureka.