KrakenD API Gateway (Community Edition)
KrakenD API Gateway | 2.9.0Linux/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.
Not a gateway but a real lifesaver
What do you like best about the product?
There are lots of reasons to choose KrakenD but to list a few I can say that its versatility is a key lifesaver. It saves lots of time & money in development besides you know that the running code is tested by millions secure, reliable and scaleable. It is developed using Go so is not vulnerable to common java vulnerabilities like log4j lately. Fast, secure and reliable software used by millions, most importantly it saves us thousands of development man-hours in microservice architecture projects.
What do you dislike about the product?
It is not very easy to find experienced tech staff since they are high in demand but you can overcome this issue with the enterprise support KrakenD provide
What problems is the product solving and how is that benefiting you?
It supports microservice architecture design patterns like circuit breaker, aggregator, throttling etc. You can mock endpoints, you can manipulate both request and response. It becomes a security shield in front of microservices. It saves time and budget a lot when developing a microservice architecture software
- Leave a Comment |
- Mark review as helpful
A year of experience with KrakenD
What do you like best about the product?
We have been using KrakenD for more than a year. It allowed us to implement a multi tenant API Gw solution which fits our needs. The best part of using KrakenD is it allows you to customize any part of the API GW by implementing your own plugin extension
What do you dislike about the product?
There are some certain functionalities that we might need and those are falling into the commercial version. Instead of packaging everything under a commercial license, there would be a nice option to provide some within the marketplace.
What problems is the product solving and how is that benefiting you?
We had some backend services which we had to provide to our third-party clients. Each client needs to access different sub-services and we had to provide a configuration-level solution that enables us to manage the API access. We easily implemented our solution using KrakenD configuration templates.
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.
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 - 54