KrakenD API Gateway (Community Edition)
KrakenD API Gateway | 2.6.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.
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
- Leave a Comment |
- Mark review as helpful
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)
Excellent all round tool for handling multiple API functions.
What do you like best about the product?
Simple, elegant and easy to use due to it's feature set.
What do you dislike about the product?
Would like to see the websockets feature available in the open source version.
What problems is the product solving and how is that benefiting you?
We have many source API feeds that need to deliver data to one application. The KrakenD API Gateway was the simplest tool for the job, and the easiest to implement.
Recommendations to others considering the product:
Simple. Install it and give it a go. You will be surprised how easy it is to get going.
Best performant and easy to configure API gateway
What do you like best about the product?
KrakenD is a highly performant and open-sourced API gateway that comes with hundreds of capabilities, such as caching, monitoring, QoS and throttling, authentication, and many more.
In addition, it is easily extendible with plugins written in Go or middleware written in Lua.
Is very well documented and its core (Lura) is developed by Linux Foundation.
Already trusted by many, definitely the best API gateway you can use both on-premise or in the cloud, serverless deployment included!!
In addition, it is easily extendible with plugins written in Go or middleware written in Lua.
Is very well documented and its core (Lura) is developed by Linux Foundation.
Already trusted by many, definitely the best API gateway you can use both on-premise or in the cloud, serverless deployment included!!
What do you dislike about the product?
The number of configuration options can be a little overwhelming initially, but fortunately, there is an official web UI to help with the config file generation.
What problems is the product solving and how is that benefiting you?
As an API gateway, it helps by improving access to internal APIs endpoints of a distributed system by allowing you to handle real-time transformations, JWT authorisation and authentication, backend resilience and the circuit breaker and more. It benefits my projects by enabling the use of very performant API gateway with much more features than other cloud API gateways.
Fast, Agile, Super Low Learning Curve and great Support!
What do you like best about the product?
The Documentation is something awesome, besides the products were made by people that already faced real challenges when building a real API initiative project.
What do you dislike about the product?
The plugins creation and extensibility capability is something that requires Golang experience, although the situation you would need it is once in a blue moon
What problems is the product solving and how is that benefiting you?
Performance is the key aspect! Everything in the solution is made to offer the best experience possible for API consumers
Recommendations to others considering the product:
Several other API Gateways tried to solve the whole problems in the world and also expected that everybody could be a top-notch user. KrakenD can be easy to learn, use, and sustain at the same time that is easy to scale up in a wide range of deployment options.
Easy to use, excellent performance and superlative support.
What do you like best about the product?
It is very easy to configure, you can have an endpoint fully working in about 5 minutes.
What do you dislike about the product?
I have no complaints so far, Kraken has met my expectations.
What problems is the product solving and how is that benefiting you?
In our case, we want to migrate our monolithic application to a microservices architecture. We have put Kraken as middleware to progressive decouple our services.
Not a gateway but a real lifesaver
What do you like best about the product?
There are lots of reasons to choose KrakenD but to list a few I can say that its versatility is a key lifesaver. It saves lots of time & money in development besides you know that the running code is tested by millions secure, reliable and scaleable. It is developed using Go so is not vulnerable to common java vulnerabilities like log4j lately. Fast, secure and reliable software used by millions, most importantly it saves us thousands of development man-hours in microservice architecture projects.
What do you dislike about the product?
It is not very easy to find experienced tech staff since they are high in demand but you can overcome this issue with the enterprise support KrakenD provide
What problems is the product solving and how is that benefiting you?
It supports microservice architecture design patterns like circuit breaker, aggregator, throttling etc. You can mock endpoints, you can manipulate both request and response. It becomes a security shield in front of microservices. It saves time and budget a lot when developing a microservice architecture software
A year of experience with KrakenD
What do you like best about the product?
We have been using KrakenD for more than a year. It allowed us to implement a multi tenant API Gw solution which fits our needs. The best part of using KrakenD is it allows you to customize any part of the API GW by implementing your own plugin extension
What do you dislike about the product?
There are some certain functionalities that we might need and those are falling into the commercial version. Instead of packaging everything under a commercial license, there would be a nice option to provide some within the marketplace.
What problems is the product solving and how is that benefiting you?
We had some backend services which we had to provide to our third-party clients. Each client needs to access different sub-services and we had to provide a configuration-level solution that enables us to manage the API access. We easily implemented our solution using KrakenD configuration templates.
showing 31 - 40