Re: service discovery
James Bayer
can you describe the architecture of your applications? do the endpoints
change often after some mircoservices have been started? your app needs some way to look up other network endpoints it needs. there are several ways to do this. * use environment variables - which is provided just-in-time when the container starts - this might be a URL for example, that routes to the CF router that might be bound to several different apps, but all the source app needs to know is the destination route represented by a FQDN and optional context path * use a service - either user a service broker or provided service that provides information to the apps that bind to it, might be a URL and authentication information, this information is also put in the apps env variables * use something like the spring cloud config service that can distribute information to clients dynamically post container start [1] * use something like the spring cloud eureka service from netflix oss that can provide dynamic information to clients using netflix ribbon, also takes in updates post container start [2] [3] [1] https://www.youtube.com/watch?v=bJvReWt2jLc [2] http://cloud.spring.io/spring-cloud-netflix/spring-cloud-netflix.html [3] http://blog.pivotal.io/pivotal-cloud-foundry/features/deploying-microservice-architectures-with-pivotal-cloud-foundry On Thu, Jun 25, 2015 at 7:47 PM, Sumanth Yamala <Sumanth.Yamala(a)sas.com> wrote: micro-service architecture. -- Thank you, James Bayer |
|