What exactly is micro in micro-clothes?

Aside from dogmatic explanation, coupling degree is the biggest change from boulder application to microservice application. Either the repeated parts in multiple modules are separated, or the inflated single application is simply separated, and these separated parts are deployed and maintained independently as services, which is micro-service.

After the split, some necessary requirements will naturally arise:

From the macro perspective of the common website architecture at present, micro-service is at a medium level. The part circled in the red box belongs to the category of micro-clothes. Including the most basic rpc framework, registration center, configuration center, as well as a broader perspective of monitoring and tracking, governance center, dispatch center and so on.

From the micro-service itself, it generally includes the following modules:

Is it a microservice just by wearing a microservice framework? Although there is a table of micro-services, there is no essence of micro-services, that is, "micro"

The premise of micro-service is that the service is divided into enough "micro" and single responsibility. Of course, the degree of division of labor and the boundary of service need to be grasped by the business.

Generalized service splitting includes application splitting and data splitting.

After application splitting, it is necessary to introduce micro-service framework for service communication and service governance, which is also the traditional definition of micro-service.

After data splitting, a series of measures need to be introduced to ensure it. Since it's not a topic related to traveling incognito, I'll just briefly explain it here: