Move away from gorilla/mux

[davidebianchi]

Is your feature request related to a problem? Please describe.

gorilla/mux toolkit is now archived https://github.com/gorilla#gorilla-toolkit and no longer maintained.

Describe the solution you'd like

We should move to another toolkit. We should talk about some possibilities. To make some minor changes to the code, we should move to a toolkit based on the http package, like echo or gin-gonic. Otherwise, we can also choose to switch to fasthttp with something like fiber.

Additional context

The gorilla toolkit remains available, so there is not hurry to do the change.

What do you prefer about the alternatives?

[fredmaggiowski]

Maybe moving to fiber could be nice since it's supposed to be faster it may help increasing the proxy throughput, however we have to make sure it is feature complete for what we currently need (here a non-complete list):

• path parameters
• oas definition (for standalone mode)
• transparent proxy out-of-the-box with response body access (without we may have to rethink how response policies are evaluated)
• Middleware management

[fredmaggiowski]

Gorilla has now been taken by a new team, shall we keep this issue open or try and stay with the lib?

[davidebianchi]

Yes, I think we could close this issue at the moment.