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.
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
- Leave a Comment |
- Mark review as helpful
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
Best Api Gateway after research
What do you like best about the product?
Really easy to install and configure, super fast
What do you dislike about the product?
Small company supporting it, but really skilled devs
What problems is the product solving and how is that benefiting you?
API proxy with good Auth/SSO intetration, we configure against a custom SSO using Oauth 2.0 really fast
Powerful, Streamlined and Elegant
What do you like best about the product?
Cherry picking a specific feature that I like about Kraken is somewhat difficult given the host of functionalities available for developers to utilize. Tools such as Greylog and Grafana are an added benefit.
What do you dislike about the product?
Like any tech, KrakenD has it's own limitations but nothing that cannot be solved by writing custom plugins. There are features that can be built to make it more robust.
What problems is the product solving and how is that benefiting you?
The fact that KrakenD becomes a single source of truth for all my API's is the biggest advantage I find.
Tons of capability with easy installation/ops
What do you like best about the product?
Simple installation and operations make KrakenD extremely likable. There are up-to-date packages for every major OS, maintained by the KrakenD developers. It's also dead simple to install manually if necessary. Many proxy-based API gateways have multiple services that interact to create the working system (Traefik, Tyk, etc.). KrakenD cuts through all of that. I also love that you can use message brokers (RabbitMQ, SQS, etc.) as API targets. This opens up a whole new world of architectural possibilities.
What do you dislike about the product?
Although the documentation is excellent in most ways—organization, examples, and covering things at an appropriately conceptual level—it is still missing a few items and you'll probably run into one of them at some point. Occasionally something is mentioned but is not quite up to date. Finally, there have been a few bugs. It's a fast development cycle and there is a rough edge here and there. But with the simple operations, it would be very easy to revert to a previous version to wait for a fix.
What problems is the product solving and how is that benefiting you?
We are now terminating SSL and Authn/z at the gateway. KrakenD is also helping us standardize our API addresses without always rewriting/rerouting existing API endpoints. Some new APIs can now even be delivered entirely via configuration rather than code. For example: KrakenD endpoint > AWS SQS message > Zapier.com > (whatever).
Recommendations to others considering the product:
Just install it and try it out, since it is so simple to start using.
KrakenD - my API Gateway choice for advanced architectures
What do you like best about the product?
As a freelance architect, I design and implement architectures for various projects. And KrakenD is usually integral part of them.
Scalability and high-load readiness 'out of the box' are precious features.
I especially like and make use of advanced features, like web sockets support, for many fintech projects ability proactively send information from backend to user wallet app for instance is
very important.
Scalability and high-load readiness 'out of the box' are precious features.
I especially like and make use of advanced features, like web sockets support, for many fintech projects ability proactively send information from backend to user wallet app for instance is
very important.
What do you dislike about the product?
Some non-technical restrictions can be an issue. Some projects I support wanted to pay in crypto for paid version of KrakenD, but it was not possible. Hopefully it will be resolved in future.
What problems is the product solving and how is that benefiting you?
1) as any API gateway - implement respective architecture approach, business angle - upgradebility, easiness of development, scalability for microservices architecture
2) specifically feature which is KrakenD "only" - communication not only initiated by 'clients', but from backend, can be very precious feature (it is in paid version only)
2) specifically feature which is KrakenD "only" - communication not only initiated by 'clients', but from backend, can be very precious feature (it is in paid version only)
showing 21 - 30