spring-cloud-dependencies

1.Dalston.SR1

2.Camden.RELEASE

3.Brixton

So for example if you are using Spring Boot 1.2 then go with Angel, 1.3 then Brixton, 1.4+ then Camden is probably your best bet. Even then you can always get things working by resolving dependency conflicts yourself.

Microservice Registration with Spring cloud using Netflix Eureka

When we start a project, we usally have all the configurations in the properties file.
As more and more services are developed and deployed, adding and modifying these properties become more complex. Some services might go down, while some the location might change. This manual changing of properties may create issues.
Eureka Service Registration and Discovery helps in such scenarios. As all services are registered to the Eureka server and lookup done by calling the Eureka Server, any change in service locations need not be handled and is taken care of
This Post is divided into 4 parts-
a.) Overview of Netflix components.
b.) Develop an Employee service to produce and consume REST API using Spring Boot.
c.) Use Eureka for Service Registration.
d.) Use Eureka for Service Discovery.

The patterns provided include Service Discovery (Eureka), Circuit Breaker (Hystrix), Intelligent Routing (Zuul) and Client Side Load Balancing (Ribbon).

Netflix Component Name	Functionality
Eureka	Service Registration and Discovery
Ribbon	Dynamic Routing and Load Balancer
Hystrix	Circuit Breaker
Zuul	Edge Server