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.
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.
- Leave a Comment |
- Mark review as helpful
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
Fast and Lightweight
What do you like best about the product?
- Lighting fast
- Easy to start with
- Feature rich
- Supports variety of backends ( http, amqp etc. )
- Easy to start with
- Feature rich
- Supports variety of backends ( http, amqp etc. )
What do you dislike about the product?
Lack of management dashboard in the open-source version of the product.
What problems is the product solving and how is that benefiting you?
Security, observability, service decoupling, protocol termination
Performant, easily configurable and a great alternative to other solutions
What do you like best about the product?
Its documentation and ease of use are very appreciated. I liked a lot its extensibility and the fact that provides awesome performance even in small instances/machines.
What do you dislike about the product?
I'd probably suggest dedicating some efforts towards OpenTelemetry (although that's related to the size of the team supporting all this, mind that is not a huge company even if the quality of the product indicates so!).
What problems is the product solving and how is that benefiting you?
It allowed me to experiment with multiple APIs and endpoints in a private setup, as a PoC for splitting some services, without the hassle of creating something too coupled to the cloud provider.
Recommendations to others considering the product:
Read the documentation, experiment and see the paid version, it may already have what you need.
Powerful, Lightweight and Easy to Implement
What do you like best about the product?
KrakenD is very light on resources which allows you to handle great amount of requests on mediocre hardware. Documentation is straightforward. While seeking features for requirements it does not try to sell you some enterprise package for some basic features. KrakenD is a single executable so you don't have to deal with complex installations. KrakenD is stateless and it loads its configuration from a JSON file. You don't have to deal with some database administration.
What do you dislike about the product?
Because KrakenD is stateless if you don't know exactly what you are doing it is easy to cause downtime. They included some nice to have plugins to the enterprise plan that I would like to use with the community edition. Also, the enterprise plan kinda limits the server/pod count that you can use.
What problems is the product solving and how is that benefiting you?
If you need to manipulate request/response bodies, routing requests to different hosts or paths, rate-limiting requests originating from clients or do authentication checks you must give KrakenD a try.
Low learning curve and simplicity by rule
What do you like best about the product?
Performance is simply amazing: 70k rps with an instance which implies low operating costs
It's a very modular and extensible solution, you can extend its plugins to add your features or needs.
One configuration file.
Amazing features to be free community edition.
It's a very modular and extensible solution, you can extend its plugins to add your features or needs.
One configuration file.
Amazing features to be free community edition.
What do you dislike about the product?
Documentation was a bit short but it has improved lately.
What problems is the product solving and how is that benefiting you?
Integration between some microservices.
Useful and easy to deploy
What do you like best about the product?
Quick and easy setup and maintenance, great performance and even better support. Kraken is really useful for us to deal with authentication, throttling and monitoring of our API ecosystem.
What do you dislike about the product?
In our case we had to introduce another layer between Krakend and our microservices in other to orchestrate some simple business rules. It would be fantastic if these really simple rules could be loaded in Krakend in some way, somthing like If-this-thn-that but in a yaml file :)
What problems is the product solving and how is that benefiting you?
For us, it has been a relief to stop dealing with user authentication at several points of the application, and have throttling tools, and monitoring from day zero.
Best API Gateway
What do you like best about the product?
Manage all our microservices in an easy way
What do you dislike about the product?
Sometimes difficult to implement some 'not' standard or complex endpoints
What problems is the product solving and how is that benefiting you?
No need to expose our endpoints publically and interconnect different endpoints to get unified responses
Recommendations to others considering the product:
Good product to interconnect all your microservices and securitize your apps
showing 31 - 40