Which tools are needed to manage microservices?
Effectively handling microservices in your CI/CD cycles requires both a private Docker image registry and a state-of-the-art microservice orchestrator that's capable of doing the following:
- Allocating and load-balancing microservices on available hardware nodes
- Monitoring the health state of services and replacing faulty services if hardware/software failures occur
- Logging and presenting analytics
- Allowing the designer to dynamically change requirements such as hardware nodes allocated to a cluster, the number of service instances, and so on
The following subsection describes the Azure facilities we can use to store Docker images. The microservices orchestrators available in Azure are each described in a dedicated chapter, namely, Chapter 6, Azure Service Fabric, and Chapter 7, Azure Kubernetes Service.
Defining your private Docker registry in Azure
Defining your private Docker registry...