Gateway RidgeISSUE #15 of 35

service mesh · sidecar proxies

Gateway GusVSTimeout Titan

Gateway Gus saysA service mesh handles service-to-service traffic via sidecar proxies — without app code.

Where a gateway handles north-south (client↔system) traffic, a service mesh manages east-west (service↔service) traffic. A sidecar proxy runs beside each service, transparently adding mTLS encryption, retries, timeouts, load balancing, and observability — no changes to application code. Tools like Istio/Linkerd provide it. Powerful, but added complexity worth it mainly at scale.

Power-ups you unlock

Manages service-to-service (east-west) traffic
Sidecar proxy per service, transparent to code
Adds mTLS, retries, timeouts, observability
Worth the complexity mainly at scale

Timeout Titan attacks — common mistakes

Adopting a mesh for a handful of services
Confusing mesh (east-west) with gateway (north-south)
Underestimating the operational overhead

Boss battleDistinguish what a gateway handles vs what a service mesh handles.

Example code

<!doctype html><html><head><meta charset="utf-8"></head>
<body style="background:#06040d;color:#e6e0ff;font-family:monospace;padding:20px"><pre>gateway: client ↔ system (north-south)
mesh:    service ↔ service (east-west), via sidecars</pre></body></html>

▶ Open the interactive comic issue

‹ Api Gateways · The Front Door Discovery · Service Registry · Dns ›