A service mesh sells policy, identity and telemetry, and delivers them by inserting a proxy next to every pod. That proxy is a full HTTP stack, so each request crosses user space twice and pays for two TLS handshakes. EBPF-based data planes move the redirect and much of the policy into the kernel, where a socket-to-socket shortcut avoids the hops. Sidecar proxy data planes keep the proxy and its L7 vocabulary. The sharper question is which layer may understand your traffic.
A sidecar puts two user-space hops and two TLS handshakes in every call, costing low single-digit milliseconds at the tail and about half a core per ten thousand requests per second.
Part One: What is being compared
Strip the vocabulary and the choice is a threshold: below it one side avoids a commitment, above it the other amortises one.
Both give every workload an identity, enforce who may talk to whom, and emit per-request telemetry, all installed by a control plane rather than by application teams.
Part Two: The arithmetic
The…