Linkerd vs Istio — Service Mesh comparison?

Question

Accepted Answer

**Comparison:**
| Criterion | Linkerd | Istio |
|---------|---------|-------|
| Proxy | linkerd2-proxy (Rust) | Envoy (C++) |
| Size | ~10MB | ~100MB |
| CPU overhead | Low | Medium |
| Latency | <1ms | 1-5ms |
| mTLS | Automatic | Requires configuration |
| Traffic splitting | Basic | Advanced |

**Linkerd:**
```bash
linkerd install --crds | kubectl apply -f -
linkerd install | kubectl apply -f -
linkerd check
kubectl get deploy -n myapp -o yaml | linkerd inject - | kubectl apply -f -
```

**Istio:**
```bash
istioctl install --set profile=default
kubectl label namespace myapp istio-injection=enabled
```

**Choice:** Linkerd — simple, fast. Istio — advanced traffic management, fault injection.

DevOps: Linkerd vs Istio — Service Mesh comparison?