Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Microservices with Consul and Nomad

Microservices with Consul and Nomad

Richard Kettelerij

September 20, 2018
Tweet

Other Decks in Technology

Transcript

  1. Agenda • Intro • Use case @ Police • Hashicorp

    stack • Consul (incl. demo) • Nomad (incl. demo) • Recap
  2. What could be improved…. • Limited automation around creating new

    VM’s • No solution for high availability • No zero-downtime deployments - Purpose-built single instance VM for each microservice -
  3. Consul • Service discovery (via HTTP and DNS) • Health

    checking • DNS (A record, SRV record) • HTTP • Files: Consul-Template • Environment variables: EnvConsul • SDKs/Frameworks: Spring Cloud Consul, Dropwizard, etc, etc
  4. Multiple datacenters test prod OpenStack tenant A test prod OpenStack

    tenant B service- service- service- service-foo service-qux Consul cluster service-bar Webserver service- service- service- service-foo service-qux Consul cluster service-bar Webserver service- service- service- service-foo service-qux Consul cluster service-bar Webserver service- service- service- service-foo service-qux Consul cluster service-bar Webserver
  5. node1 Nomad Consul & Nomad cluster node2 service-bar
 node1 service-foo


    node3 service-qux
 service- qux
 service- fox
 public-node1
  6. Recap • Why did we do this? High availability •

    What did we gain? • High availability • Location transparency • Zero-downtime / rolling-upgrades • Resilience against machine failures