What if extending your API gateway didn’t mean forking the damn thing — or worse, drowning in source code?
Yeah, you read that right. Most gateways talk a big game about plugins. In reality? You’re knee-deep in boilerplate before lunch.
Take KrakenD. Solid tool. But their modifier setup? A slog. Here’s the original gripe, straight from the source:
var ModifierRegisterer = registerer(“my-plugin”) func (r registerer) RegisterModifiers(f func( name string, factoryFunc func(map[string]interface{}) func(interface{}) (interface{}, error), appliesToRequest bool, appliesToResponse bool, )) { f(string(r)+”-request”, r.requestHandler, true, false) }
Then your actual modifier receives an interface{} that you type-assert against a RequestWrapper you defined yourself.
Sixty lines. Minimum. Just to register. Copy-paste wrappers. Type assertions everywhere. It’s indirection squared — and you’re the sucker holding the bag.
Why Does API Gateway Extension Still Suck in 2024?
Look. We’ve had extensible servers since Apache’s mod era. Nginx modules followed, clean and C-powered. Yet API gateways? Stuck in the ’90s.
Teams fork ‘em. Why? Plugins demand you grok internals. Or hack JSON configs till they break. KrakenD’s no villain — it’s just symptomatic. Powerful, sure. Entry cost? Brutal.
Kono flips the script. Built for Go teams who hate that noise. No forking. No source dives. Plugins? Four methods: Info(), Type(), Init(), Execute(). Boom.
And middleware? Standard http.Handler wrapping. If you’ve touched Gin or Echo, you’re home.
But here’s my unique hot take: This echoes WordPress’s plugin boom in the 2000s. Back then, PHP hacks ruled. Plugins killed ‘em — simple hooks, massive ecosystem. Kono? Same vibe for API gateways. Bold prediction: Forked Kongs and Tyk variants wither in two years. Teams flock to low-boilerplate winners.
Can Kono Really Slash That Boilerplate?
Hell yes. Check this Execute method:
func (p *Plugin) Execute(ctx sdk.Context) error { resp := ctx.Response() if resp == nil || resp.Body == nil { return nil } // read body, transform, replace resp.Body = io.NopCloser(bytes.NewReader(newBody)) return nil }
Direct http.Request, http.Response access. No wrappers. Snakeify plugin — JSON to snake_case? 100 lines total. Thirty SDK, seventy logic. That’s artisan work, not plumbing.
Compare to KrakenD’s factory funcs and extra_config JSON. Kono’s SDK? Constants, PluginInfo struct, Context. Done.
Short version: It works because it’s honest. No magic. Clear contracts. Your brain thanks you.
I’ve tinkered. Built a header injector in 20 minutes. No docs binge. No GitHub spelunking.
Kono shines for real-world tweaks — auth, transforms, logging. Recompiling too slow? Enter Lumos.
Lua scripting. But smart.
Common trap: Embed Lua in Go. Bindings bloat. KrakenD does it — load spikes, exposed surface tiny.
Lumos? Separate LuaJIT process. Unix socket. Length-prefixed JSON. Microsecond latency — same container, no net.
Script gets full request JSON. Returns ‘continue’ with mods or ‘abort’ with status. No SDK install. Pure LuaJIT speed — 10x interpreted Lua.
Why care? Token validation at runtime. Path rewrites. Header injections. Zero gateway restarts.
Genius. Scales without gateway bloat.
Is Kono Just Hype — Or DevOps Salvation?
Skeptical? Fair. Open source loves PR spin. Kono’s GitHub? Lean. Active. No vaporware.
Docs crisp: starwalkn.github.io/konodocs. Try the snakeify example. Feels like writing tests, not plugins.
Corporate gateways like Kong? Enterprise tax. Forks everywhere — custom auth, rate limits. Kono nixes that. Small surface means teams own it.
Downsides? Young project. Ecosystem tiny vs KrakenD’s maturity. But that’s the trade: Simplicity now, or complexity forever?
My verdict: Pick simplicity. Forking’s a maintenance trap — I’ve seen teams drown in it. Kono’s your escape hatch.
And that WordPress parallel? Spot on. Plugins turned a blog tool into CMS king. Kono could do it for gateways — if devs bite.
Give it a spin. github.com/starwalkn/kono. Worst case? You learn Go plugins right.
🧬 Related Insights
- Read more: Open Source Vulnerabilities Hit Four-Year Low in 2025: Backlog Cleared, But New Threats Surge
- Read more: Claude Browses Its Own Chat and Debates Consciousness With Itself
Frequently Asked Questions
How do you extend a Kono API gateway?
Drop a Go file implementing four methods. Compile. Load. No source reads, no forking.
Kono vs KrakenD: Which for plugins?
Kono if you hate boilerplate. KrakenD if you need battle-tested scale — but expect the 60-line tax.
What’s Lumos in Kono?
LuaJIT sidecar for dynamic scripts. Unix socket comms. Perfect for hot auth tweaks without restarts.
One last jab: If your gateway forces forking, fire the architect. Kono shows better.
