Chapter 4. Adding Services to the Mesh
In the previous chapter, you learned how to deploy Consul on Kubernetes or VMs. The next step to using Consul is to add your services into the mesh. From there, you will be able to use Consul to increase security, observability, and reliability.
A service is “added to the mesh” by registering it with Consul, deploying its sidecar proxy, and ensuring that all communication is routed through that proxy. On Kubernetes, this is done via a simple pod annotation. On VMs, you have a bit more work to do: you need to register your service with Consul, deploy its sidecar proxy, and configure routing.
This chapter and subsequent chapters use an example application I built for the book to illustrate Consul’s functionality. After following the exercises with the example application, you will be well equipped to add your own services to the mesh.
Birdwatcher Example Service
To try out the service mesh, you first need some services. You’re going to deploy a basic application called Birdwatcher. Birdwatcher consists of two microservices: frontend and backend.
The frontend service hosts a UI as shown in Figure 4-1. Every time you click Shuffle, a new bird is shown.
Figure 4-1. The frontend service hosts the UI for the Birdwatcher service
The frontend service uses the backend service’s API to retrieve new birds. Whenever frontend makes a call to backend ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access