Consul: Discover your Services (GOTO Berlin 2015)

There is a strong trend to split large systems in to smaller and smaller parts and distribute them over numerous machines. Whether you just call it scaling, redundancy or even microservices, after a certain point you need new mechanisms to support this. Mechanisms that provide an overview which services are in place and where. Services also need to be monitored and finally they need to find each other.

Consul is one of a new breed of solutions that help with service discovery. Consul is a high availability solution that can even be used across data centers. Service information can be distributed quickly across the whole cluster. Consul offers interfaces for service discovery via REST, DNS and even template mechanisms. It also includes a Key-Value Store, distributed locks and health checking.

Starting with Consul is usually simple. We will show the basics but also a more complex setup that can be used in production.

Transcript

1. Consul: Discover your Services Oliver Fischer
 @sweblogtweets 
 Jörg Müller
 @JoergM
2. Jörg Müller @JoergM Hypoport AG Oliver Fischer @sweblogtweets E-Post Development GmbH
3. Why are we talking about Consul?
4. Distributed Systems are the new normality
5. Problem Areas Service Discovery Monitoring Orchestration Configuration
6. What exactly is Service Discovery?
7. Static Configuration
8. Semantic DNS
9. DNS and Loadbalancer
10. Discovery via Registry Service Registry register
11. Using Consul for Service Discovery
12. How does this work?
13. Local agents everywhere
14. Server are cluster 
 state aware
15. Jim? Jim is dead! Jim is dead! Jim is dead! Jim is dead! Communication between cluster nodes
16. Interaction of agents
17. Complex example
18. Real World Use Case
19. DNS?
20. DNS? -> No
21. REST-API?
22. REST-API? -> No
23. Consul & HAProxy
24. Show case
25. DEMO
26. But there is more…
27. Features of Consul
28. Consul Service registry
29. Consul Service registry DNS Server Example on Github
30. Consul Service registry DNS Server Example on Github HTTP API
31. Consul Service registry DNS Server HTTP API Key Value Store
32. Consul Service registry DNS Server HTTP API Key Value Store Locks Example on Github
33. Consul Service registry DNS Server HTTP API Key Value Store Locks Remote Execution
34. Consul Service registry DNS Server HTTP API Key Value Store Locks Remote Execution Watches & Events Example on Github
35. Consul Service registry DNS Server HTTP API Key Value Store Locks Remote Execution Watches & Events Example on Github Checks
36. Consul Service registry DNS Server HTTP API Key Value Store Locks Remote Execution Watches & Events Checks Encryption and ACLs
37. Consul Service registry DNS Server HTTP API Key Value Store Locks Remote Execution Watches & Events Checks Encryption and ACLs Multiple Datacenters
38. Consul Service registry DNS Server HTTP API Key Value Store Locks Remote Execution Watches & Events Checks Third party integrations Encryption and ACLs Multiple Datacenters
39. Summary
40. State of Consul
41. Difficulties today
42. The potential rises while using it
43. More on Consul Getting started: https://consul.io/intro/index.html Documentation: https://consul.io/docs/index.html Our examples: https://github.com/JoergM/consul-examples
44. Q & A