A simple api gateway from scratch written in golang

<p>Modern APIs need rate limiting, authentication, caching, and observability — but running a dedicated gateway server adds cost and complexity. Cloudflare Workers lets you build

<p>There are plenty of times you want to delegate "let this request through, or block it" to a wasm filter inside Envoy. API gateways, service mesh boundaries, L7 checkpoints. The

<p>How it works:</p> <p>Request arrives at an OpenAI-compatible endpoint<br /> Classifier detects task type + complexity<br /> Adaptive router picks the highest-scoring model for

<p>You migrated. Traffic is flowing. ReferenceGrants are in place. The controller reconciliation loop is clean. And then — quietly, without a single alert firing — things start

<h1> I got bored and wrote a circuit breaker </h1> <p>A few years ago I was working at a fintech company. We had an integration with a payment gateway. Critical one — money

<p>Most tutorials show you how to build an API. Fewer show you what sits in front of the API in a real production system.</p> <p>This project is about that middle layer. A gateway

<p><strong>TL;DR: We measured failover latency across three AI gateways (Bifrost, LiteLLM, Portkey) during 30 days of production traffic at Nexus Labs. Bifrost added 11ms p99

<p>Webhooks look simple at first: receive an HTTP request, forward it somewhere, return 200 OK.</p> <p>That simplicity disappears the moment the system becomes