Service meshes have emerged as a widely-used component of the cloud-native stack because they add critical features around visibility, reliability, and security in a way that minimizes developer involvement.
The perfect service mesh implementation wouldn’t use a general-purpose proxy, but would instead use a service mesh specific proxy—one that does no more than the mesh needs and that is written in a performant language with strong security guarantees like Rust.
The heart of any service mesh is the proxy. The proxy serves as the data plane and determines the features, functionality, and performance of your mesh
Jason Morgan