Service Mesh¶
Service mesh is the next generation service mesh for cloud native applications, built on the open-source technology of Istio. It provides a complete non-intrusive microservices governance solution to unify the governance of complex multicloud and multicluster environments, offering service traffic governance, security governance, service traffic monitoring, and traditional microservices (SpringCloud, Dubbo) capabilities as infrastructure.
DCE's service mesh is compatible with the native Istio open-source service mesh and provides native Istio access management capabilities. At a higher level, a service mesh helps reduce the complexity of service governance and alleviate the pressure on development and operations teams. The service mesh seamlessly integrates with the container management platform and serves as infrastructure support for the microservice engine, enabling unified management of various microservice systems through a single platform.
Key Capabilities¶
-
Mesh Creation and Management
Supports hosted, dedicated, and external mesh modes, covering mesh creation, deletion, and capacity management, with an operations-free managed control plane.
-
Traffic Governance
Configure weighted, content-based, and TCP/IP routing policies with virtual services, destination rules, and gateway rules for dynamic intelligent routing and elastic traffic management.
-
Traffic Monitoring
Visually displays link information, abnormal service responses, and excessively long response latency, with traffic topology for faster problem localization.
-
Security Governance
Provides peer authentication, request authentication, and authorization policies to secure service-to-service communication with mTLS.
-
Sidecar Management
Inject sidecars by namespace or workload, with sidecar resource optimization, traffic passthrough, and log level adjustment.
-
Mesh Gateway
Create and manage mesh gateway instances to provide a unified north-south traffic entry for services in the mesh.
Workflow¶
Using the service mesh typically involves two phases, deployment and integration followed by governance and observation: administrators deploy the module, create a mesh, and integrate clusters; business users then inject sidecars and start using traffic governance, security governance, and traffic monitoring capabilities.
flowchart LR
A["① Install and deploy<br/>Deploy the service mesh module"] --> B["② Create a mesh<br/>Hosted · dedicated · external"]
B --> C["③ Integrate clusters<br/>Clusters join the mesh"]
C --> D["④ Inject sidecars<br/>Namespace · workload"]
D --> E["⑤ Govern and observe<br/>Traffic · security · monitoring"]
click A href "../install/install/"
click B href "../user-guide/service-mesh/"
click C href "../user-guide/cluster-management/join-clus/"
click D href "../user-guide/sidecar-management/ns-sidecar/"
click E href "../user-guide/traffic-governance/" | Step | Role | Description |
|---|---|---|
| ① Install and deploy | Platform administrator | Deploy the service mesh module in the DCE cluster |
| ② Create a mesh | Platform administrator | Create a mesh in hosted, dedicated, or external mode |
| ③ Integrate clusters | Platform administrator | Add one or more clusters to the mesh for unified management |
| ④ Inject sidecars | Business user | Inject sidecar proxies by namespace or workload |
| ⑤ Traffic governance and traffic monitoring | Business user | Configure routing and security policies, and monitor service status in real time |
Product Advantages¶
DCE's service mesh has the following advantages compared to other products:
| Advantage | Description |
|---|---|
| Simple and easy to use | No need to modify any business code or manually install proxies — just enable the service mesh feature to experience non-intrusive service governance |
| Policy-based intelligent routing and elastic traffic management | Weighted, content-based, and TCP/IP routing rules; HTTP session persistence; rate limiting and outlier detection; network connection management; service authentication, authorization, and auditing |
| Graphical application panoramic topology | Visualized monitoring of link information, abnormal service responses, and long response latency, with invocation chain information for faster problem localization |
| Enhanced performance and reliability | Control plane and data plane are hardened and performance-optimized on top of the community version |
| Multi-cloud, multi-cluster, and multi-infrastructure | Operations-free managed control plane with unified governance, security, and monitoring; unified service discovery and management for containers, VMs, and other infrastructures |
| Protocol extension | Supports the Dubbo protocol |
| Traditional SDK integration | Applications built with Spring Cloud, Dubbo, and other traditional microservice SDKs can be migrated to the cloud native mesh environment without extensive code modification |
Quick Start¶
More Resources¶
-
Features
A complete list of service mesh capabilities, from mesh management and traffic governance to security and monitoring.
-
Architecture
Understand the overall architecture of the service mesh, its control plane components, and system namespaces.
-
FAQ
Common questions and solutions related to service mesh usage.
-
Troubleshooting
A continuously updated troubleshooting handbook covering mesh creation, cluster integration, sidecar issues, and more.
Download Center Learn about d.run Token Factory Learn about d.run AI OS View the Service Mesh User Guide (PDF)