Extending your API gateway without forking it

Most API gateways are extensible in theory. In practice, you end up reading source code for hours before writing a single line of business logic. I ran into this while building Kono. Before deciding on the plugin architecture, I looked at how KrakenD handles request/response modification. Their approach is powerful but has real entry cost: you implement a ModifierRegisterer symbol, call RegisterModifiers with factory functions, copy-paste RequestWrapper and ResponseWrapper interface definitions...