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.
Head of Architecture
What do you like best about the product?
Single point for APIs. Licencing model. Flexibility, simplicity and specially the Krakend's support team.
What do you dislike about the product?
Direct integration with RabbitMQ was a bit disappointing although it may suffice for simple scenarios, it was not robust enough for our use cases. This is something that they could improve.
What problems is the product solving and how is that benefiting you?
Single point of contact. API security hardening. API normalization.
- Leave a Comment |
- Mark review as helpful
Excellent documentation and container images that are ready to use to evaluate
What do you like best about the product?
I’ve had a great experience using this API Gateway! One of the standout features is the excellent documentation. It’s well-structured, easy to follow, and provides clear explanations for a wide range of use cases.
What truly sets it apart, though, is the inclusion of live working examples. These aren’t just basic snippets—you get fully functional Docker images that are ready to use right out of the box. This makes it incredibly easy to test and deploy different configurations without wasting time on setup.
What truly sets it apart, though, is the inclusion of live working examples. These aren’t just basic snippets—you get fully functional Docker images that are ready to use right out of the box. This makes it incredibly easy to test and deploy different configurations without wasting time on setup.
What do you dislike about the product?
Limited API monetization alternatives. I was able to find only one plugin. Maybe I didnt search enough
What problems is the product solving and how is that benefiting you?
Moving from SaaS to our OnPremise API Gateway
The best-documented API gateway among the competitors, with the most helpful people behind it.
What do you like best about the product?
- The documentation is great, compared to other competitors
- The focus on being a good API Gateway, no focus on side projects that lower the quality of the gateway
- The people behind it are very helpful - they really want to help and search for a solution
- The flexible configuration feature
- It was easy to deploy in our Kubernetes cluster
- Go plugin support, with a handy builder image supplied
- Uses security-first principles like zero-trust security policy
- The focus on being a good API Gateway, no focus on side projects that lower the quality of the gateway
- The people behind it are very helpful - they really want to help and search for a solution
- The flexible configuration feature
- It was easy to deploy in our Kubernetes cluster
- Go plugin support, with a handy builder image supplied
- Uses security-first principles like zero-trust security policy
What do you dislike about the product?
- Because of the stateless nature of everything, some business requirements are challenging to implement. But I can see the reasoning - speed matters.
- We were advertised the upcoming proxy plugins feature, but when it was dropped, we did not receive a formal update. It would be nice to keep track of which customers are interested in which features.
- Lack of an authentication system on a global level, but only endpoint level. Unmapped endpoints are thus not authenticated and we needed to rethink our plugins for things to work as they used to.
- Low customization options for authentication responses (returning different reasons in case of missing token, expired token, incorrect signature, ...).
- Not easy to do a transparent migration from another gateway system, but this will most likely be the case for every other gateway on the market. We need to integrate KrakenD to work exactly as our old gateway did.
- Its native plugin system is using Go, which I dislike. We cannot bump dependency versions when KrakenD's binary is using them already. This slows down patches and forces us to group them together and update them when KrakenD does. It feels archaic to have to deal with this in a modern programming language.
- We were advertised the upcoming proxy plugins feature, but when it was dropped, we did not receive a formal update. It would be nice to keep track of which customers are interested in which features.
- Lack of an authentication system on a global level, but only endpoint level. Unmapped endpoints are thus not authenticated and we needed to rethink our plugins for things to work as they used to.
- Low customization options for authentication responses (returning different reasons in case of missing token, expired token, incorrect signature, ...).
- Not easy to do a transparent migration from another gateway system, but this will most likely be the case for every other gateway on the market. We need to integrate KrakenD to work exactly as our old gateway did.
- Its native plugin system is using Go, which I dislike. We cannot bump dependency versions when KrakenD's binary is using them already. This slows down patches and forces us to group them together and update them when KrakenD does. It feels archaic to have to deal with this in a modern programming language.
What problems is the product solving and how is that benefiting you?
Replacing our current API Gateway, ultimately lowering maintenance.
Supporting future API Monetization & usage logging
Supporting future API Monetization & usage logging
KrakenD Enterprise Version Review
What do you like best about the product?
What I like best about KrakenD is how easy it is to integrate it to your systems. It is also easy to implement the endpoint definitions. I like its ability to allow you to implement your own custom plugins to manage authorization and authentication based on your business needs. I also like how responsive its support team is, helping with enterprise level issues on a timely manner.
What do you dislike about the product?
What I don't like about KrakenD is its inability to run the application locally in debug mode. KrakenD offers metrics and logging mechanisms, but when running the application locally using your IDE of choice, it is not possible to have debug mode enabled and debug your code line by line. When writing custom plugins, it would be useful to run debug mode to make sure that each line of code in the plugin is working as expected.
What problems is the product solving and how is that benefiting you?
For my organization KrakenD solved the problem of multiple authentication providers. To consume our private cloud APIs, users can choose between two types of authentication tokens being okta and authblue. We did not have a solution to enable the two authentication tokens in the same API gateway endpoint. However, after acquiring KrakenD Enterprise Version, we were able to integrate multiple authentication providers which solved a tremendous need for our customers to consume private cloud APIs.
We use KrakenD to power the Public API
What do you like best about the product?
It is generally intuitive to configure and reliable. We've never had issues with it crashing or anything like that.
What do you dislike about the product?
Some of the documentation is not clear or needs more examples. For example, the rate limiter docs are quite confusing to me. I would also find it useful to have some repository with sample implementations with comments around what each configuration item does.
I'd also really like to see the possibility to customise access logs in a better way so that it is more filterable in tools such as datadog.
I'd also really like to see the possibility to customise access logs in a better way so that it is more filterable in tools such as datadog.
What problems is the product solving and how is that benefiting you?
KrakenD handles our token validation, routing to different backends, rate limiting and even region routing via a custom plugin.
Very stable and extendable API gateway
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.
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.
Easy to develop, implementation and use
What do you like best about the product?
I have migrated an older api manager to KrakenD and it is faster, secure and powerfull. It is easy to develop, deploy and use for customers.
What do you dislike about the product?
Sometimes it is difficult search a valid example
What problems is the product solving and how is that benefiting you?
We have security risk with older api manager and we have some problems to develop new features.
KrakenD gives us new tools, features and security updates often
KrakenD gives us new tools, features and security updates often
A modern API gateway
What do you like best about the product?
The development team is really easy to work with. They listen to feedback from the community and implement changes based on it. Their documentation is also very good, and it is easy to learn how to accomplish whatever you want.
What do you dislike about the product?
The hardest thing for me has been trying to debug issues with my config file. It lets you know that there is an issue, but it would be nice if it told me a specific line of the file where the issue was.
What problems is the product solving and how is that benefiting you?
It is serving as our API gateway, and that allows all of our apis to access each other. It is more preformant than our old one, and requires fewer resources to run.
A Powerhouse API Gateway That Delivers Top-Tier Developer Experience with Effortless Simplicity
What do you like best about the product?
We chose KrakenD over other gateway platforms because:
- It's easy to operate and configure: JSON or YAML, you choose.
- You can managed the configuration via GitOps practices.
- It supports OpenTelemetry integration for observability.
- It supports multiple backend protocols (HTTP, gRPC, Lambda, among many others).
- It's easy to manipulate data and compose .
- It's easy to extend via custom plugin development at different stages of the request pipeline.
- It's easy to operate and configure: JSON or YAML, you choose.
- You can managed the configuration via GitOps practices.
- It supports OpenTelemetry integration for observability.
- It supports multiple backend protocols (HTTP, gRPC, Lambda, among many others).
- It's easy to manipulate data and compose .
- It's easy to extend via custom plugin development at different stages of the request pipeline.
What do you dislike about the product?
There is only one thing that still bothers me and it's its logging. The available customisations on how a statement is logged are still quite limited.
I'd really like to see a more customisable logging implementation.
I'd really like to see a more customisable logging implementation.
What problems is the product solving and how is that benefiting you?
We have been able to migrate our legacy endpoints and domains to the newly created single entrypoint for all our services, and at the same time, a top notch gateway to support our microservice architecture.
We have been able to switch our legacy endpoints with no downtime for our user base by leveraging a combination of
- use virtualhost plugin
- data manipulation
- custom request/response plugins
We have been able to switch our legacy endpoints with no downtime for our user base by leveraging a combination of
- use virtualhost plugin
- data manipulation
- custom request/response plugins
Does what it claims to do
What do you like best about the product?
KrakenD has proven to have both a product that delivered the outcome we were looking for and be an organisation that is pleasant to work with.
The Gateway is a critical part of our architecture for our customer-facing console and was easier to implement than other systems we have worked with in the past. When we did have questions, KrakenD responded promptly. KrakenD have also listened to suggestions for product enhancements with an open mind and provided reasoned feedback .
The Gateway is a critical part of our architecture for our customer-facing console and was easier to implement than other systems we have worked with in the past. When we did have questions, KrakenD responded promptly. KrakenD have also listened to suggestions for product enhancements with an open mind and provided reasoned feedback .
What do you dislike about the product?
It is our preference to manage systems using an API, e.g REST, gRPC, GraphQL or similar. At the time of our evaluation and subsequent purchase, KrakenD does not offer such a facility. After discussing with KrakenD and our SRE team, we looked using CI/CD with configuration under source control.q
What problems is the product solving and how is that benefiting you?
Authenticates requests from a variety of sources and routes them correctly.
showing 1 - 10