1 Introduction
Service governance (Service Governance) microservices that remove the business and the rest can belong to the service governance category, integration configuration, background service integration DB, MQ, Cache, service registration discovery, soft load, log, Metrics, call chain buried point, limit Streaming, fuse, security and access control, REST/RPC, serialization/binary/Json, underlying communication HTTP/TCP, unified exception handling, documentation.
The following five points are mainly introduced below:
1) Registration and discovery
In microservices, if there are call dependencies between microservices, the dependent service is first registered in the registry, then the service is called to obtain the service address information from the registry, and finally the dependent service is called.
2) Service monitoring
Microservice monitoring includes call topology, monitoring (Metrics), log (Logging), call tracing (Trace), etc. between services. Obtain a clear and intuitive understanding of the calling relationship and status among many services through monitoring.
3) Service security
Security, different microservices carry their own unique business responsibilities. For business-sensitive microservices, authentication and authorization of access to other services is required.
4) Service control
Distribute service governance policies to microservices in real time and take effect.
5) Service upgrade
There are different versions of microservices. In the process of version change, it is necessary to control the calls between microservices in order to smooth the microservice version change. This smooth change is distributed to different versions of services based on traffic characteristics (access parameters, etc.) and percentages through gray-scale release, blue-green release, and A/B testing.
Microservice governance, the usual practice is to introduce microservice R&D