https://wouter.sh/categories/patterns/Recent content in Patterns on Wouter in 't VeldHugo -- gohugo.ioen-usTue, 20 Oct 2026 12:22:49 +0200https://wouter.sh/posts/sse-behind-a-shared-gateway/Tue, 20 Oct 2026 12:22:49 +0200https://wouter.sh/posts/sse-behind-a-shared-gateway/At work several teams push live updates to browsers: an order changes state, a label is ready, a list should refresh. Each team built its own WebSocket API for that. Meanwhile the rest of their traffic moved behind a shared Envoy gateway (the one from an earlier post), and the WebSocket APIs could not follow. The managed WebSocket APIs we used only come with a public, regional endpoint (AWS whitepaper), and our gateway only forwards to private ones.https://wouter.sh/posts/self-service-routes-shared-envoy-gateway/Sun, 11 Oct 2026 09:43:45 +0200https://wouter.sh/posts/self-service-routes-shared-envoy-gateway/At work we run one Envoy gateway in front of many teams’ private APIs. Requests reach it through a CDN and a load balancer, and Envoy matches the Host header to one virtual host per team before forwarding to that team’s API. It started the way shared gateways usually start: one config file in the gateway repository, and a pull request to it every time a team needed a route. That works for three routes.