KrakenD API Gateway (Community Edition)
KrakenD API Gateway | 2.9.0Linux/Unix, HAQM Linux HAQM Linux 2 AMI - 64-bit HAQM 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.
Great team experience with KrakenD
What do you like best about the product?
Ease of customization with the creation of plugins in addition to several that it already provides, KrakenD was able to serve us perfectly to create an effective multitenancy solution.
What do you dislike about the product?
I would like to see the possibility of exporting and importing openapi schemas in the opensource version.
What problems is the product solving and how is that benefiting you?
design an effective multi tenancy solution.
- Leave a Comment |
- Mark review as helpful
Better and faster API gateway
What do you like best about the product?
Our backend architecture became a little messy, and we were looking for solutions to make the microservices better. We found KrakendD and implementation was smooth, thanks to the clean documentation.
What do you dislike about the product?
Haven't hit the limitation yet, but they have enterprise versions and might to upgrade later.
What problems is the product solving and how is that benefiting you?
KrakenD provides API gateway, and we can manage our APIs with this platform, it provides a lot of option while giving really good performance.
Krak The Performance with Krakend
What do you like best about the product?
API aggregation . Endpoint addition specifically with microservice. Api response modifier .
custom Template configuration for config.json also known as flexible configuration.
custom Template configuration for config.json also known as flexible configuration.
What do you dislike about the product?
We can't add new endpoints in real time . Need to restart krakend server . Hot reload is there but it's too risky for production. Also custom plugins develent documentation is very limited
What problems is the product solving and how is that benefiting you?
The Main Problem calling different api of microservice for user with multiple call. The API aggregation feature of Krakend is resolved this issue. Also Respond modifier also one the useful feature
Efficient and easy
What do you like best about the product?
Ease of configuration and well structured documentation. Adding new endpoints is a breeze.
What do you dislike about the product?
Took a bit of a deep-dive to get running in the way we needed on our infra.
What problems is the product solving and how is that benefiting you?
An easily configurable and explorable API gateway. Much easier to have the dev team embrace it and take ownership of maintaining the solution.
An Api Gateway easy to start with and powerful to end with
What do you like best about the product?
It's so easy to start with it with some basic configuration. The excellent documentation makes it easy. It's straightforward and fast. The stateless architecture makes it very scalable
What do you dislike about the product?
Complex scenarios takes time to understand. It's not widely used so the community is limited. I would appreciate real world example to compare.
What problems is the product solving and how is that benefiting you?
We used it for orchestrating calls to out api from the backend for frontend. It scales so well and gives use excellent performance. The config file makes easy to modify by the different teams.
It's easy to use and maintain. The docs are very helpful and complete enough for us to understand.
What do you like best about the product?
The documentation and plugins are helpful. I appreciate the logging dashboard, monitoing and scalability.
What do you dislike about the product?
Some docs are still incomplete like for logging and things. I hope we can find the full logging and monitoring demo via KrakenD youtube channel
What problems is the product solving and how is that benefiting you?
The microservices problems and throttle handling
Easy to setup and efficient. Really interesting architecture.
What do you like best about the product?
Fast to setup. Quality. Flexibility. Efficiency. Performance
What do you dislike about the product?
Paid enterprise features - a necessary evil
What problems is the product solving and how is that benefiting you?
We were in need of common interface and features for our APIs. A gateway approach came to mind, and, after evaluation, krakenD was our choice.
Really an excellent product
What do you like best about the product?
Fast, lightweight, easy to implement and integrate into automatic CI/CD pipelines and microservices. Also, as middleware, it is very flexible and very useful when it comes to unifying APIs.
What do you dislike about the product?
the restrictive part of the enterprise product, we are currently using the free version.
the restrictive part of the enterprise product, we are currently using the free version.
the restrictive part of the enterprise product, we are currently using the free version.
What problems is the product solving and how is that benefiting you?
1. apigateway
2. multi country api integration layer
3. replacing qvantel graphql as a middleware
2. multi country api integration layer
3. replacing qvantel graphql as a middleware
Still an easy to use high performance API Gateway
What do you like best about the product?
After 3 years of productive use, still these are my favourite properties of KrakenD:
- Easy setup.
- Easy configuration.
- Comprehensive Docs.
- No performance issues.
- Easy setup.
- 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.
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.
showing 21 - 30