Network Service Mesh vs Terway
Network Service Mesh
networkservicemesh.ioTerway
github.comSide by side
| Figure | Network Service Mesh | Terway |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | Yes | — |
| Linux | Yes | Yes |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Container Networking Software | 8.3 (#3) | 7.0 (#22) |
Plans
In their own words
Network Service Mesh
Network Service Mesh connects workloads across clusters and clouds through a hybrid, multi-cloud IP service mesh. Each workload can connect independently to zero or more Network Services, regardless of where it runs. The project says it works with an existing CNI without requiring changes to Kubernetes or workloads. Services can provide connectivity, security, and observability at Layer 3 and above, carrying IP or Ethernet payloads.
Clients may be Kubernetes pods, virtual machines, or physical servers. They authenticate independently, currently using SPIFFE IDs, and need authorization to attach. Clients request and close virtual wires over gRPC and can monitor connection status through a streaming call. Endpoint selection offers composition, selective composition, topology awareness, and scale from zero. A service may also provide domain-scoped DNS for connected pods. The architecture describes integration with Istio, Linkerd, Consul, and Kuma. Network Service Mesh is a CNCF sandbox project and is free and open source. Its run guide lists Docker, Go, a Kubernetes cluster, and kubectl as prerequisites; most examples require at least two worker nodes.
Terway
Terway is a free, self-hosted CNI plugin for Alibaba Cloud Kubernetes (ACK), built on Alibaba Cloud ENI technology and running on Linux. Each Pod receives its own network stack and IP address. Pods on one ECS instance communicate directly, while traffic between ECS instances uses VPC ENIs without VxLAN encapsulation. ENI mode allocates interfaces to Pods, and trunking can provide independent ENIs for flexible security-group and switch settings. Node pools can be configured for exclusive ENI use. Terway supports Kubernetes NetworkPolicy, traditional security groups, egress control, dual-stack IPv4 and IPv6, and multi-cluster networking. The project uses eBPF for protocol-stack acceleration and describes the result as low latency and high throughput. Supported environments include Kubernetes ACK, Alibaba Cloud VPC/ENI, Alibaba Cloud Linux 3/4, ContainerOS, and Ubuntu. In self-hosted clusters, trunking is unavailable; the README also marks VPC Network Mode and Exclusive ENI Mode as deprecated.