Transforming Kong into an AI Gateway on GCP: Managing LLM Tokens, MCP, and Agentic Traffic
Most platform teams didn't set out to build "AI infrastructure." They already had Kong running in front of hundreds of REST services on GKE, handling …
Latest Architecture news from Tech News
Most platform teams didn't set out to build "AI infrastructure." They already had Kong running in front of hundreds of REST services on GKE, handling …
Nine years. That's how long I've been building WordPress booking engines for vacation rentals. Didn't plan it. Just sort of happened. One client led t…
Some context first: we were running on GKE Autopilot, where the Gateway API just works out of the box. Google manages the CRDs and the underlying load…
There is common point of confusion. what's the different between REST API vs. HTTP API in AWS and what's the different between them and a traditional …
The Problem With How Most Teams Run Kong If you set up Kong the default way, everything lives together — routing, policy enforcement, plugin execution…
Every backend project I've worked on eventually hits the same wall. You start clean — one service, simple routes, everything works. Then slowly the re…
Introduction "Fluidize your AI subscription quotas and maximize the value of every penny." This is the No.73 article in the "One Open Source Project p…