We’re getting to an exciting part of our microservices build—the point where we actually bring everything together. So far, we’ve built an operating model, a microservice design, an infrastructure foundation, and two working microservices. Now, we’ll take all those pieces and put them together in a single implementation.
We’ll be covering a lot of ground in this chapter. We’ll build a new infrastructure environment called staging. Next, we’ll augment our code repository with a container delivery process. With a container ready to go, we’ll implement a deployment process using the Argo CD GitOps tool. When we’re done, we’ll have an architecture that looks like Figure 10-1.
Figure 10-1. Staging deployment
Note
Because of the scope of what we need to cover, we’ll only deploy the flight information microservice. However, you can use all the mechanisms we describe here to deploy the reservations service as well.
To make all this work, we’ll be using three different GitHub repositories with their own pipelines and assets (as shown in Figure 10-2). One of the reasons we’ve done it this way is that it matches up well with the operating model we defined in Chapter 2 and gives each of our teams their own responsibilities and domains to work in.
Figure ...
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.
