Book Image

Simplifying Service Management with Consul

By : Robert E. Jackson
Book Image

Simplifying Service Management with Consul

By: Robert E. Jackson

Overview of this book

Within the elastic and dynamic nature of cloud computing, efficient and accurate service discovery provides the cornerstone for all communications. HashiCorp Consul facilitates this service discovery efficiently and securely, independent of the operating environment. This book will help you build a solid understanding of both the concepts and applications of HashiCorp Consul. You'll begin by finding out what you can do with Consul, focusing on the conceptual views of configuration samples along with Terraform code to expedite lab environment and hands-on experimentation, which will enable you to apply Consul effectively in your everyday lives. As you advance, you'll learn how to set up your own Consul cluster and agents in a single datacenter or location and understand how Consul utilizes RAFT and GOSSIP protocols for communication. You'll also explore the practical applications of primary Consul use cases, including communication flows and configuration and code examples. With that knowledge, you'll extend Consul across datacenters to discuss the applicability of multiple regions, multiple clouds, and hybrid cloud environments. By the end of this Consul book, you will have the tools needed to create and operate your own Consul cluster and be able to facilitate your service discovery and communication.
Table of Contents (12 chapters)
1
Section 1: Consul Use Cases and Architecture
6
Section 2: Use Cases Deep Dive

Major Tom, are you OK?

Whenever we deal with communications, there is almost always some level of feedback that is required to ensure that the receiver is available. This is the entire instigator of the phrases we all know so well, such as can you hear me now?. Anybody who has had to deal with network load balancers or system monitoring should be no stranger to the term health check. This is exactly what Consul can employ within every service definition. Although a health check isn't a required part of a service definition, I can't imagine why anybody would want to define and deploy a service without one!

In the realm of network load balancers or system monitoring, health checks were defined and orchestrated by some centralized form of intelligence. This means that if a load balancer managed 10 services running across 100 different nodes, the load balancer would need to track 1,000 health checks. This can not only cause some scaling issues as the services grow but it also...