Istio official Chinese version of the document

http://istio.doczh.cn/

https://istio.io/docs/concepts/what-is-istio/goals.html

Why use Istio?

In the transition from monolithic applications of distributed micro-service architecture, developers and maintenance personnel faced with many challenges, using Istio can solve these problems. The term & Grid Service (Service Mesh) is generally used to describe the interaction of these micro-network of service applications, and between them. As the size and complexity increase, more and more difficult to understand and service grid management. It needs including service discovery, load balancing, failover, and monitoring and metrics collection is usually more complex operation and maintenance needs, such as A / B testing, canary release, current limiting, access control and end-to-certification.

Istio provides a complete solution by providing insight into the behavior of the grid for the entire service and operational control to meet the diverse needs of micro-services applications. It provides a number of key features unified in the service network:

Traffic management. API calls and the flow of traffic between control services, making calls more reliable, and make the network more robust in harsh conditions.
Observability. Understand the dependencies between services, as well as the nature and flow of traffic between them, providing the ability to quickly identify problems.
Policy enforcement. The interaction between the organization's strategy applied to the service, to ensure that access policies enforced, good distribution of resources among consumers. Change the policy by configuring the grid instead of modifying the application code.
Identity and Security Service. Provide grid services to verify the identity, and provide the ability to protect service traffic so that it can flow on the credibility of different networks.

In addition, Istio was designed for scalability to meet the different deployment needs:

Platform support. Istio designed to be run in a variety of environments, including cross-cloud, preset environment, Kubernetes, Mesos and so on. Initially focused on Kubernetes, but soon will support other environments.
Integration and customization. Policy enforcement components can be extended and customized to integrate with existing ACL, logging, monitoring, quotas, auditing solutions.

These features greatly reduce the coupling between the application code, the underlying platform and strategy. Reducing coupling allows service easier to implement, but also to make it easier operation and maintenance personnel between the mobile application deployment environment, or replaced with a new strategic plan. Therefore, the result is that applications become easier to move from nature.

Reproduced in: https: //my.oschina.net/xiaominmin/blog/1835289