What do you like best about the product?

In short, it's stability, the performance and the extendability via plugins. Also, the file-based configuration, including templating, is something we value a lot.
It took us only 3-4 weeks to develop a robust solution that suits our needs, including Golang plugins.
We run KrakenD in production for a couple of months now and haven't had any issues since we deployed it. The uptime is flawless.
The team at KrakenD is super quick in responding to questions and issues. They have been great to work with.
Thanks to the Docker image and the file-based configuration, it integrated very neatly into our stack.

What do you dislike about the product?

One part for which we use KrakenD is to proxy requests. One minor point regarding this is that the configuration file gets somewhat lengthy with duplication. There is a technical reason for this, and it's not hindering us from using KrakenD. Further, a lot of the duplication can be decreased by using the templating that is offered by KrakenD, which we do.

What problems is the product solving and how is that benefiting you?

We use KrakenD as the single interaction and entrypoint for our Frontend applications. It has benefited us greatly in establishing a unified way of interaction and also helped us aligning our product teams around this approach using a API gateway.