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

This article introduces the knowledge of "what are the core features of Istio". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

As the micro-service architecture becomes more and more complex, it is necessary to decouple "business services" from "infrastructure" and split a micro-service process in two:

A process implements the business logic, biz, that is, the white square above

A process implements the underlying technical architecture, proxy, that is, the blue square above, load balancing, service discovery and governance, and call chain. A lot of infrastructure, etc., are implemented on this layer.

After such decoupling:

Biz, whether invoking services or providing services, only communicates locally with the local proxy

All cross-network communication is carried out through proxy

If you want to talk about ServiceMesh, you have to mention Istio, which is a popular practice in ServiceMesh. Today, let's talk about what Istio does.

Voiceover: don't be out of date.

What is Istio?

Istio is the product landing of ServiceMesh, and some of its key descriptions are:

(1) help establish connections between microservices, help the R & D team better manage and monitor microservices, and make the system architecture more secure.

Voice over: Istio helps you to connect, secure, control, and observe microservices.

(2) help micro-services to be decoupled in layers, and the decoupled proxy layer can focus more on providing infrastructure capabilities, such as:

Service discovery (discovery)

Load balancing (load balancing)

Failure recovery (failure recovery)

Service Measurement (metrics)

Service Monitoring (monitoring)

A _ testing B test (A _ amp B test)

Grayscale publishing (canary rollouts)

Current limit and speed limit (rate limiting)

Access control (access control)

Identity authentication (end-to-end authentication)

Voiceover: admire, just put together ten, in fact, SM can also provide more basic service functions.

(3) make the business engineering team and the infrastructure team work more efficiently, focus on their own work, and better empower each other.

Voiceover: it's still decoupling.

How does the official website of Istio boast about itself?

Voiceover: another way to ask this question is "Why do people use Istio?"

Istio is very powerful, and if you want to implement ServiceMesh, you must use Istio because:

(1) the above N basic functions can be realized by adding a side car agent (sidecar proxy) to the existing server, and the application does not need to change the code, or only needs to change a little code.

Voiceover: do you believe it?

(2) you can manage and view the above N basic functions by controlling the background, simply changing the configuration, and clicking a button.

(3) the following features are explained by Istio in this section:

Load balancer supports multi-protocol, HTTP, gRPC, WebSocket, TCP

Fine-grained flow control through routing, retry, and failover

Through pluggable policy layer and configurable API, it can support traffic access control, speed limit and quota management.

Automatic measurement, log collection, call tracking

Service-to-service authentication

What are the core features of Istio?

Istio highlights five key features it provides:

(1) flow Control (traffic management)

Voiceover: circuit breaker (circuit breakers), timeout, retry, high availability, multirouting rules, AB testing, grayscale release, distribution of traffic according to percentage, etc.

(2) Security (security)

Voiceover: encryption, identity authentication, service-to-service access control, container-to-container permission control in K8S, etc.

(3) visible (observability)

Voiceover: tracking, monitoring, data collection, through the control of the backend to fully understand the uplink and downlink traffic, service links, service operation, system performance, domestic micro-service architecture, this part is relatively lacking.

(4) platform irrelevant (platform support)

Voiceover: K8s, physical machine, their own virtual machine is fine.

(5) Integration and customization (integration and customization)

Voiceover: customizable extension function.

The boasting and features of Istio are very attractive to many foreign companies that provide private network services through RESTful, but they may not achieve a good courting effect compared with the domestic micro-service architecture:

The domestic RPC framework is basically TCP, and multi-protocol support may not be necessary.

In the RPC framework, routing, retry, failover, load balancing, and high availability are the most basic.

Flow control, speed limit and quota management are the contents of service governance, which are the icing on the cake in the initial stage of micro-service architecture.

Automatic measurement, system entry and exit data collection, call tracking, observable and controllable background are indeed the most attractive.

For service-to-service identity authentication, micro-services are basically intranet access, which is just the icing on the cake at the beginning of the architecture.

That's all for "what are the core features of Istio?" Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

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.