The Problem With How Most Teams Run Kong
If you set up Kong the default way, everything lives together — routing, policy enforcement, plugin execution, live traffic handling. One deployment doing all the things.
It works. Until it doesn't.
When traffic spikes, you scale up. But you're scaling the control plane too, which barely does anything at runtime. You're paying compute for config management that gets touched only when something changes — not on every request.
That was us. Scaling more than we needed to, paying for it, and not realizing why.
