Shulou(Shulou.com)06/03 Report--

This article mainly explains "how to understand Service Discovery in ASM practice". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "how to understand Service Discovery in ASM practice".

I. componentization

Therefore, when the project is large and complex enough and the requirements are vertical enough, how to evolve the overall structure of the project becomes quite important. If the project is split, it is an urgent problem to be solved. Componentization is one of the more correct solutions.

The essential idea is to disassemble the whole project according to the demand type dimension (or other abstract dimension). Each module is designed according to the principle of open to extension and closed to modification. Under such guidance, the project naturally divides and governs it, simplifies the complexity and divides it into parts. This is often called modularization (componentization).

Personal opinion: call it a component or a module, it's just a difference in abstract dimensions, there's nothing to struggle with.

The significance of componentization for the project lies in macroscopic decoupling and concrete cohesion. This idea is often mentioned in the design module: high cohesion and low coupling.

The "benefits" brought by this are also obvious. if the complex work is simple enough, then the division of the team will be more scientific and the implementation will be more efficient. After all, you only need to be responsible for your own one-mu land, "the pot will be easier to divide".

This also seems to be an application under the assembly line mode, whether it is good or bad, as a worker, I do not like to judge anything, after all, I am also a member of the assembly line. Who in the world is willing to put on shackles?

To clarify the core and significance of componentization, we need to think about how to land. In order to completely split and decouple, in addition to the design on the interface, compilation isolation must also be considered. At this stage, many experienced students should be aware of the thorny problem: since it is oriented to the interface and compiler isolation, how to get the implementation behind the interface?

At this point, it's time to face the problem of service discovery (or interface discovery).

Second, service discovery

Let's use a picture to describe the content of the above conversation:

From the figure, we can see that the component solution here is to add an interface layer, which is the implementation layer. In order to achieve compilation isolation, all implementation layers can only rely on the interface layer, so that for the implementation layer, you can not see the implementation of other modules, and will not interfere with other modules.

Therefore, how to make it convenient for modules to perceive the implementation of other modules through service discovery is particularly important.

Thank you for your reading. the above is the content of "how to understand Service Discovery in ASM practice". After the study of this article, I believe you have a deeper understanding of how to understand Service Discovery in ASM practice, and the specific usage needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.