Shulou(Shulou.com)05/31 Report--

This article will explain in detail how to analyze Service Mesh from the perspective of service governance and distributed development history. The content of the article is of high quality, so the editor shares it for you as a reference. I hope you will have some understanding of the relevant knowledge after reading this article.

In the soft load world, distribution is a very important field, the world is changing, the soft load field is also changing. As early as 10 years ago, technology giants basically focused on the field of middleware, such as Spring, Mybatis, Struts, etc., without considering the unified management and scheduling of service clusters. The reason why Service Mesh is so popular at present, in fact, has a lot to do with the development of computers, distribution and services, and it is also a process that technology development must go through.

Stand-alone minicomputer period

Large and unified Big Mac application

Stand-alone application of vertical split

Moore's Law of computer-performance bottleneck of single computer

Commercial IBM machines are too expensive

Clustering period

Switch from high-end commercial IBM machines to ordinary PC machines

Hardware load balancing bottleneck

Optimal allocation of Machine Resources

Software load balancing

Service period

From application to service

Remote call (RPC)

Virtual IP address (manage service address through VIP)

Manage complex service dependencies

Service governance

Soft-load products of service governance, such as Duboo's ZooKeeper registry and SpringCloud's Eureka registry, maintain mapping (subscription relationships) between providers and consumers.

Bypass load

Micro service period

Service refinement

Architecture lightweight

With the evolution of distributed architecture, micro-service is a watershed, when engineers really realize the complexity of distributed architecture itself. before micro-service, distribution is developing in the direction of doing more and doing fine. for example, clustering, service management, service governance and so on, are all architecture extension and evolution. However, while micro-service is refined, it is proposed for the first time that lightweight, after micro-service, the distributed architecture enters the process of architecture contraction, and the complexity of the architecture itself is imperceptible to business engineers.

New era of Service Grid (Service Mesh)

Multilingual differences

The complexity of an exponential system architecture

Sidecar Design (Linkerd)

Docker helps Sidecar

First generation service grid

The problem of confusion of micro-service relationship is solved from the data logic level, but the configuration control is not realized, and the connectivity problem of Sidecar is solved.

Second generation service grid

Added configuration control functions for services, such as Istio

This is the end of how to analyze Service Mesh from the perspective of service governance and distributed development history. I hope the above content can be helpful to you and learn more knowledge. If you think the article is good, you can share it for more people to see.

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.