Microservices With Spring Boot and Spring Cloud Netflix

Capgemini APPS Evolve! Summit 2016
Bad Soden, 3rd of March 2016

Krzysztof Sobkowiak (@ksobkowiak)

The Apache Software Foundation Member
Senior Solution Architect at Capgemini



  • Domain Architecture

  • Basic Technologies

  • Service Discovery

  • Load Balancing

  • Communication

  • Resilience

Domain Architecture

Three Microservices

domain architecture bg

Architecture Considerations

  • Separate data storages

  • Lots of communication

  • Bounded Context

  • Don’t modularize microservices by data

Basic Technologies

HSQL Database

  • In memory database

  • Not really suited for production use

  • Keeps the example application easy

Spring Data JPA

  • Provides support to build repositories based on Spring and JPA

  • Support for Querydsl predicates and thus type-safe JPA queries

  • Pagination support, dynamic query execution, ability to integrate custom data access code

public interface PersonRepository extends PagingAndSortingRepository<Person, Long> {
  List<Person> findByLastName(@Param("name") String name);

Spring Data REST

  • Provides the domain objects with little effort via REST

  • Can hide certain data elements

  • Can be configured flexibly

  • Tight coupling between the internal model and the interface can be decoupled

@RepositoryRestResource(collectionResourceRel = "people", path = "people")
public interface PersonRepository extends PagingAndSortingRepository<Person, Long> {
  List<Person> findByLastName(@Param("name") String name);

Spring Boot

  • It can be pretty small…​

  • Predefined packages/starters available

  • Can generate WAR or JAR file

public class ControllerAndMain {

  public String hello() {
    return "hello";

  public static void main(String[] args) {
      ControllerAndMain.class, args);

Writing a single service is nice…​

…​but no microservice is an island

Challenges of Distributed Systems

  • Configuration management

  • Service registration & discovery

  • Routing & balancing

  • Fault tolerance (Circuit Breakers!)

  • Monitoring

Spring Cloud

spring cloud overview bg

Spring Cloud Components

  • Security - supports the implementation of security mechanisms

  • Config - centralizes and dynamically adjusts the configuration

  • Bus - sends dynamic configuration changes for Spring Cloud Config

  • Sleuth - distributed tracing with tools like Zipkin or Htrace

  • Zookeeper - supports Apache Zookeeper

  • Consult - facilitates Services Discovery using Consul

  • Cluster - implements leader election and stateful patterns using technologies like Zookeeper or Consul

  • Stream - supports messaging using Redis, Rabbit or Kafka

Spring Cloud Netflix

  • Zuul - routing

  • Ribbon - Load Balancer.

  • Hystrix - resilience in Microservices.

  • Turbine - can consolidate monitoring data from different Hystrix servers.

  • Feign - option for an easier implementation of REST clients

  • Eureka - Service Discovery

Service Discovery

Why Eureka?

  • REST based service registry

  • Supports replication

  • Caches on the client

  • Resilient

  • Fast, but not consistent

  • Foundation for other services

Eureka Client

  • Registers automatically with the Eureka server under a defined name

  • Can access other Microservices

  • Integrates Load Balancing with Ribbon using

    • DiscoveryClient, FeignClient

    • Eureka aware RestTemplate (sample later)

  • @EnableDiscoveryClient or @EnableEurekaClient

  • Dependency to spring-cloud-starter-eureka


Eureka Server

  • @EnableEurekaServer

  • Dependency to cloud-starter-eureka-server

public class EurekaApplication {
  public static void main(String[] args) {
    SpringApplication.run(EurekaApplication.class, args);

Eureka Dashboard

eureka dashboard

Load Balancing


  • Decentralized, client side Load Balancing

  • No bottle neck

  • Resilient

  • Registration information might be inconsistent

RestTemplate & Load Balancing

  • @RibbonClient

  • Dependency to spring-cloud-starter-ribbon

@RibbonClient(name = "ribbonApp")
... // Left out other Spring Cloud / Boot Annotations
public class RibbonApp {

  private RestTemplate restTemplate;

  public void callMicroservice() {
    Store store = restTemplate.getForObject("http://stores/store/1", Store.class);


Zuul Routing

  • One URL to outside

  • Internal many microservices

  • Maps route to server registered on Eureka, e.g. /customer/** to CUSTOMER

  • Allows to internally change the structure of the Microservices

  • REST or HTML gui

zuul proxy bg

  • @EnableZuulProxy, dependency to spring-cloud-starter-zuul

  • Alternatively @EnableZuulServer - no routing, uses filters

Eureka, Zuul & Ribbon Interactions



  • Microservices can deal with the failure of other Microservices

  • Even if a called Microservice is not available, they will still work


  • Enables resilient applications

  • Call in other thread

  • Won’t block request handler

  • Can implement timeout

Circuit Breaker with Hystrix

  • Circuit open after certain number (error threshold) of failed calls

  • If open, calls not directed to called system

  • After configured window circuit closes

Hystrix with Annotations

  • Java proxies automaticaly created

  • Annotations of javanica library

  • @EnableCircuitBreaker or @EnableHystrix, dependency to spring-cloud-starter-hystrix

@HystrixCommand(fallbackMethod = "getItemsCache", commandProperties = {
  @HystrixProperty(name = "circuitBreaker.requestVolumeThreshold", value = "2")

public Collection<Item> findAll() {
  this.itemsCache = ...
  return pagedResources.getContent();

private Collection<Item> getItemsCache() {
  return itemsCache;

Hystrix Dashboard

hystrix dashboard


  • Aggregates data from different Hystrix systems

  • The state of all Circuit Breakers can be summarized on a single dashboard

turbine bg


  • @EnableTurbine and @EnableEurekaClient, dependency to spring-cloud-starter-turbine

  • Can use @EnableHystrixDashboard to display dahsboard on the same instance

  • Consolidated data determined by the configuration

    clusterConfig: ORDER
  appConfig: order


  • Easy to create new project

  • REST integrated

  • messaging supported

  • Simple deployment

  • Uniform operations