KrakenD API Gateway (Community Edition)
KrakenD API Gateway | 2.5.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.
Easy to use high performance API Gateway
What do you like best about the product?
- Easy setup.
- Easy configuration.
- Comprehensive Docs.
- No performance issues.
- Easy configuration.
- Comprehensive Docs.
- No performance issues.
What do you dislike about the product?
Nothing at all.
Until now, there was no reason to complain.
Until now, there was no reason to complain.
What problems is the product solving and how is that benefiting you?
We needed an API Gateway for our APIs, and KrakenD fitted our requirements best.
Also licensing and prices are pretty fair.
Also licensing and prices are pretty fair.
- Leave a Comment |
- Mark review as helpful
Fast, powerful and easy to configure
What do you like best about the product?
I used krakend community edition api gateway in every projects that I worked on. It's very fast to set up and run, very easy to configure, it uses very few resources and has a lot of useful plugins that solve most of the problems that you can encounter. For example in the most case I use plugin for jwt and roles validation on endpoints, plugin for modify request/response headers or plugin for limiting the requests per seconds on endpoints. It has a well done and complete documentation and the authors on GitHub are very active and answers very fast if you have an issue. I love this api gateway.
What do you dislike about the product?
There are only two things that I dislike of Krakend. The first thing is that it is not possible to create wildcard path for endpoints (an architectural decision). The second thing is the conflicts with endpoints that you can encounter for example if you define two endpoints with the same http method like this: "/api/exhibitions/search", "/api/exhibitions/{exhibitionCode}". But this is caused by a limitation of the router package (a Go package called gin-gonic/gin router) used in the core of Krakend.
What problems is the product solving and how is that benefiting you?
Krakend helps me to protect every single microservices that exposes rest apis by evaluating the jwt, it also checks the roles inside the jwt for allowing calls to the services only to certains users.
Lightweight, high performance API Gateway
What do you like best about the product?
It's fast and straightforward to get started with basic to moderate use cases. There is an excellent slack channel where the developers are very active in replying to posts. KrakenD is well architected to be easy to deploy and monitor using industry standards such as openmetrics. It has zero dependencies when starting up and running, making it highly reliable.
What do you dislike about the product?
The documentation often misses essential details that can waste time when implementing more complex use cases.
What problems is the product solving and how is that benefiting you?
KrakenD provides security and protection functionality at a gateway level. Features such as authentication, authorization, request validation and circuit breaker shield the backend from issues that could otherwise cause downtime across a wide range of backend services. Having these features at the gateway ensures implementation consistency and prevents time wasted on undifferentiated heavy lifting.
An inspiring code structure
What do you like best about the product?
I am constantly inspired by their code organization and structure for golang projects. Its incredibly solid and well done which breeds excellence over the whole technology stack. There is a reason why KrakenD is brutally fast and stable :)
What do you dislike about the product?
If you require an "invisible" api gateway, similar to a reverse proxy with more functionality, then KrakenD is probably not what you are looking for.
It will fall more along the lines of an intermediate layer for your applications. in the end, it will fulfill the same requirements but in a different way.
It will fall more along the lines of an intermediate layer for your applications. in the end, it will fulfill the same requirements but in a different way.
What problems is the product solving and how is that benefiting you?
Our main use cases include:
* Avoiding manking many frontend calls for different services that end up traveling the internet, instead we now call once and KrakenD calls the downstream services
* Rate limiting standards for all the services
* Centralized User Authentication to avoid implementing code in every single downstream app
* Avoiding manking many frontend calls for different services that end up traveling the internet, instead we now call once and KrakenD calls the downstream services
* Rate limiting standards for all the services
* Centralized User Authentication to avoid implementing code in every single downstream app
High Performant API Gateway with a great support and tech team behind
What do you like best about the product?
The best thing about KrakenD is its extreme simplicity and design to be operated with a GitOps approach. You can have all the endpoints your team controls in one or multiple repositories and trigger their deployment via automated CI/CD pipelines, ensuring nothing breaks when going to production. Additionally, there is no need to have external auditing tools, as git provides this.
What do you dislike about the product?
Even though the functionality is extensively documented on the web page, I missed a quick introduction or tutorial to go from zero to live with best practices.
What problems is the product solving and how is that benefiting you?
KrakenD helps to expose mashups made of small parts of internal APIs publicly, ensuring users are appropriately validated and with the proper permissions.
Straight-forward and easy to use software
What do you like best about the product?
Easy configuration, nearly plug'n play. We had a running gateway in a matter of minutes.
What do you dislike about the product?
Really nothing, maybe the fact that some advanced configuration required a deeper reading into the documentation.
What problems is the product solving and how is that benefiting you?
We wanted to set up a way to normalize and standarize our endpoints in the context of a completely new backend architecture and performance tuning, so it was perfect to establish an independent from services software that we can control where to point services at.
Feature-rich API gateway tool with high performance
What do you like best about the product?
The API gateway tool offers:
- a high degree of customizability
- wide feature selection of throttling, rate-limiting, transformations, filters, load balancing, circuit breakers etc.
- very lightweight deployment
- very high processing performance
- good developer experience due to good documentation
- no vendor lock-in
- a high degree of customizability
- wide feature selection of throttling, rate-limiting, transformations, filters, load balancing, circuit breakers etc.
- very lightweight deployment
- very high processing performance
- good developer experience due to good documentation
- no vendor lock-in
What do you dislike about the product?
These disadvantages still complicate the introduction of KrakenD:
- no managed deployment
- no OpenAPI3 support
- no developer portal
- the enterprise plan is comparatively pricey
- no managed deployment
- no OpenAPI3 support
- no developer portal
- the enterprise plan is comparatively pricey
What problems is the product solving and how is that benefiting you?
It helps implement a lightweight API gateway enabling higher API stability and security.
The high degree of customizability helps address a broad set of API traffic management problems other gateways are too inflexible to solve.
It serves specifically well in introducing an API gateway with limited resources for companies at the start of their API journey.
The high degree of customizability helps address a broad set of API traffic management problems other gateways are too inflexible to solve.
It serves specifically well in introducing an API gateway with limited resources for companies at the start of their API journey.
Recommendations to others considering the product:
If you are looking for an easy-to-use tool to start with and know that it is self-managed this is one of the best choices to start with.
Fast and easy
What do you like best about the product?
It is very easy to start with. It takes just a few minutes to get it up and running even the first time. Documentation is very simple and straightforward. It is written in Golang which makes it very lightweight and easy to extend.
What do you dislike about the product?
Some basic features are implemented into the enterprise version which means that they will never be a part of the community edition.
What problems is the product solving and how is that benefiting you?
KrakenD is very useful for optimising API structure for different frontends while keeping the backend services standard and simple. It is also dealing with authentication and acts as an extra security layer for the backend.
A good solution
What do you like best about the product?
Session handling is easy using Kraken. it's a good tool.
What do you dislike about the product?
Pricing needs to be reduced. Need to introduce a free plan.
What problems is the product solving and how is that benefiting you?
Used for session management in a microservice architecture.
Elegant solution for application gateway
What do you like best about the product?
The authentication and response manipulation functionality are the best features of KrakenD
What do you dislike about the product?
Restrictions on POST endpoints without plugins.
What problems is the product solving and how is that benefiting you?
Application routing, load balancing and centralized authentication
showing 11 - 20