Service Mesh
Sidecars applied estate-wide, and the scale at which that pays.
4 to work through
-
advanced
A platform is evaluating a service mesh. What should be checked before adopting, and what is the honest justification?
2 min answer -
advanced
A platform runs 2000 pods across 300 services and is about to put a sidecar proxy in every pod. Roughly what does the fleet cost in memory and control-plane work before a single request is served, and which number grows fastest as the platform doubles?
3 min answer -
advanced
A proposal for an internal tool serving 50 requests per second specifies a service mesh, distributed tracing, three databases, a message broker, distributed locks and multi-cluster deployment. What do you cut and what do you keep?
3 min answer -
advanced Multiple choice
After a mesh rollout, one service's p99 rises from 30 ms to 70 ms, but only for calls to services in other namespaces. Same-namespace calls are unchanged. CPU on both sides is flat and the proxy reports no errors. What is the most likely cause?
3 min answer
3 terms in this topic
Control-Plane Push Amplification
The property that one endpoint change can force a configuration push to every proxy in the fleet, making control-plane work scale with proxies multip…
conceptMesh Control Plane
The component that configures and coordinates a service mesh's data plane proxies, distributing policy, identity and routing rules.
toolService Mesh
Moving connection-level concerns — discovery, retries, timeouts, mTLS, telemetry — out of application code and into a proxy alongside every service.
Neighbouring topics
Architecture Patterns
General material on architectural patterns and their trade-offs.
Layered Architecture
The default shape, its clarity, and where a technical partition fails.
Event-Driven Architecture
Publishing facts, and trading comprehensibility for decoupling.
Pipes and Filters
Independent transformation steps composed into a pipeline.
Publish/Subscribe
Broadcast to every subscriber, as distinct from work distribution.
Competing Consumers
Scaling throughput with instances, at the cost of ordering.
Saga
Local transactions with compensating actions across services.
CQRS
Separate models for writing and reading, each optimised for its job.
Event Sourcing
The event log as the system of record, with state as a projection.
Outbox
Making the event atomic with the business write it describes.
Strangler Fig
Incremental replacement behind a routing facade.
Anti-Corruption Layer
Translating a foreign model at the boundary so it does not leak in.
Sidecar & Ambassador
Cross-cutting behaviour in a co-deployed process.
API Gateway
A single entry point for policy, routing and protocol translation.
Backend for Frontend
A narrow backend per client experience, owned by that client's team.
Cell-Based Architecture
Complete isolated copies each serving a subset of customers.
Sharding Patterns
Directory versus embedded keys, logical shards and rebalancing.
Materialized Views
Precomputed query results, refreshed incrementally or in full.
Orchestration vs Choreography
A coordinator that knows the flow, or services that react to events.