KrakenD API Gateway (Community Edition)
KrakenD API Gateway | 2.7.2Linux/Unix, Amazon Linux Amazon Linux 2 AMI - 64-bit Amazon Machine Image (AMI)
Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
The simplest API Gateway with a great performance
What do you like best about the product?
The best of KrakenD is its extensibility. You can extend it with their existing plugin ecosystem and flexible configuration. Also, creating a plugin for it is effortless, since it's a very well-written API Gateway code.
What do you dislike about the product?
It has a very good telemetry integration with many services like Prometheus, Datadog, Grafana…, but I miss having OpenTelemetry, since nowadays it has become a standard.
What problems is the product solving and how is that benefiting you?
KrakenD enabled our company to have some BFF (Backend for frontend) to escalate our APIs. Also, since is a very performant Gateway, we did it while lowering costs compared to other Gateways.
Recommendations to others considering the product:
There is a channel in the Gophers Slack called #KrakenD where the creators answer questions.
- Leave a Comment |
- Mark review as helpful
Stateless and cost-effective API Gateway for our microservices
What do you like best about the product?
It does not depend on anything else rather than a simple configuration file. Guarantee scaling needs without having to increase the cost linearly as you have to do in other API gateway cases. Better pricing for scale needs and better performance without vendor lock-in.
What do you dislike about the product?
I would like to have some kind of backoffice with a dashboard containing metrics and graphs to monitor all the different services connected to the API Gateway .
What problems is the product solving and how is that benefiting you?
I have migrated from a monolith to a microservices-based architecture, preventing to change the public specification of our APIs. It was a nice way to progressively migrate all our architecture without having to stop delivering new features meanwhile we were doing the migration
showing 51 - 52