Gateway API

📖 Series Navigation: ← Previous Chapter: Part 9 — Cookie vs. SessionStorage vs. LocalStorage | Next Chapter: Part 11 — Client-Side Rendering (CSR) vs. Server-Side Rendering (SSR) in the Modern AI Era → | Series Hub Part 10: Envoy Gateway vs. Cilium eBPF Service Mesh: Kernel Performance & Layer 7 Governance Showdown Answer-first: Envoy Gateway excels as a North-South Edge API Gateway with dedicated Envoy pods for advanced L7 policies (WAF, JWT, rate limiting, AI token quotas). Cilium eBPF dominates East-West cluster networking by bypassing the TCP/IP stack via sockops and cutting 92% RAM with node-level Envoy daemons. The 2026 standard combines both. ...

Tech Radar: Stateless MCP 2.0 & Kubernetes Gateway API Architecture Answer-first: The Model Context Protocol revision transitions tool execution to stateless JSON-RPC 2.0 over HTTP and SSE while eliminating sticky-session bottlenecks across enterprise clusters. Combined with Kubernetes Gateway API (agentgateway) and Redis 7.4 context hydration, this architecture horizontally scales thousands of Go 1.25 MCP server pods, enforces SPIFFE mTLS authentication, and reduces P99 latency below 12ms. Prerequisite: Readers should have production familiarity with Kubernetes Gateway API v1.2+ (GatewayClass, HTTPRoute, BackendTLSPolicy), Envoy L7 filter chains, JSON-RPC 2.0 wire framing, SPIFFE/SPIRE X.509 SVID workload identity attestation, and concurrent network programming in Go 1.25+ and Redis 7.4 Cluster. ...