KCNA ยท Cloud native principles and patterns
Service mesh and sidecar proxies
Sidecar proxy model, mTLS, traffic management, REST vs gRPC, Envoy, Istio, Linkerd at a conceptual level.
Key points
- A service mesh handles service-to-service traffic outside app code.
- A data plane of proxies (for example Envoy in Istio, or Linkerd's own proxy) runs as sidecars next to each workload and provides mTLS, load balancing, retries and metrics.
- A control plane (Istio's istiod, Linkerd's control plane) configures the proxies and issues certificates.
Source: https://istio.io/latest/docs/ops/deployment/architecture/
Practice questions
What does mTLS provide between two services in a mesh?
- Encrypted traffic with both sides authenticating each other
- Only the server proves its identity
- Automatic scale to zero
- Conversion of REST calls into gRPC
Show answer
Answer: A. Encrypted traffic with both sides authenticating each other
Mutual TLS encrypts traffic and both sides present certificates, so each verifies the other's identity. Plain TLS authenticates only the server.
Which capabilities does a service mesh typically provide?
- Traffic splitting between versions
- Mutual TLS between workloads
- Building container images
- Request-level metrics and tracing hooks
- Scheduling pods onto nodes
Show answer
Answer: A. Traffic splitting between versions, B. Mutual TLS between workloads, D. Request-level metrics and tracing hooks
Traffic management (canary splits), mTLS and request-level telemetry are classic mesh features. Building container images and scheduling pods are not mesh jobs.
True or false: gRPC is built on HTTP/2 and typically uses Protocol Buffers, while REST commonly uses HTTP/1.1 with JSON.
Show answer
Answer: True
True. gRPC uses HTTP/2 with protobuf binary messages; REST APIs commonly use JSON over HTTP, though REST can run on HTTP/2 too.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
