Chapter 5. Designing a Deployment Monitor Microservice
During a deployment, whether it is for your microservices or something else, you are inevitably going to have to start and stop services and applications as a part of your deployment process. I am assuming here you have a managed, continuous deployment process, or, at the very least, not a manual process (yes, I've seen big clients manually promote across environment by hand picking change sets!).
In this chapter we will learn:
- How to create a deployment monitor microservice
- How to create messages specifically for this microservice
- How to handle events during a deployment
- How to tell if a deployment has taken too much time
Now, let's talk a little about what a typical deployment scenario might look like:
When a deployment starts, one or more services and applications affected in that environment (QA, staging, production, and so on) will have to be stopped to be updated. When this happens, the system is basically inoperable for the time period...
