krakend-ce VS apisix-dashboard

KrakenD: A high-performance open-source API Gateway. It helps application developers release features quickly by eliminating all the complexities of SOA architectures while offering a unique performance.

This is my first foray into NGINX, and it seems my desired use-case is a bit different/left field. We're attempting to utilize NGINXaaS (Azure PaaS) to act as an API Gateway for some of our on-premise APIs. We were trailing KrakenD prior for this, but are moving toward NGINX as there's a desire to move everything PaaS (where appropriate). Our current KrakenD instance is configured to host a different set of URI than what the backend is configured for, IE:

Check what configuration language (JSON/Yaml) and style (Declarative/Imperative) chosen API Gateway support. It is not so crucial but sometimes you might ask: Does it have a user-friendly GUI and drag&drop easy config option? Some open-source projects like Tyk, Krakend.io, and Apache APISIX have built-in no-code possibly visual editing dashboards. You can even import all your APIs descriptions from a JSON.

KrakenD and Lura https://github.com/krakendio/krakend-ce https://github.com/luraproject/lura

I was trying to look up the license for that project and the repo linked from the footer of their website is https://github.com/krakendio/krakend-ce#readme (Apache 2), but because I just did a web search for krakend there is also https://github.com/luraproject/lura#readme which says it's from the Linux Foundation (also Apache 2)

Is KrakenD some kind of generic term, or does that project just have a complex history?

https://github.com/krakendio/krakend-ce api gateway built using lura

With various access control models and implementation methods available, constructing an authorization system for backend service APIs can still be challenging. However, the ultimate goal is to ensure that the correct individual has appropriate access to the relevant resource. In this article, we will discuss how to enable the Role-based access control(RBAC) authorization model for your API with open-source API Gateway Apache APISIX and Open Policy Agent (OPA).

The API Create phase is the first stage in the API product lifecycle management process where you design, orchestrate, transform, document, and test your API. At this stage, modern API gateways like Apache APISIX can be helpful to build your API from scratch or import API definitions from a range of sources like OpenAPI YAML/JSON structure to register Route and Upstreams.

Apache APISIX is an API Gateway. By default, it stores its configuration in etcd, a distributed key-value store - the same one used by Kubernetes. Note that in real-world scenarios, we should set up etcd clustering to improve the resiliency of the solution. For this post, we will limit ourselves to a single etcd instance. Apache APISIX offers an admin API via HTTP endpoints. Finally, the gateway forwards calls from the client to an upstream. Here's an overview of the architecture and the required certificates:

One of the key features of modern API Gateways such as Apache APISIX is its support for GraphQL APIs. APISIX makes it easy to manage and scale GraphQL APIs using its flexible configuration system and powerful plugins. One such plugin is the degrapghql plugin, which allows us to convert the GraphQL API into a REST API. In this post, we will explore this feature with an example.

Secure your API: Use an to secure API Gateway by adding authentication, rate limiting, and other security features. It reduces the number of exposed APIs, organizations can reduce surfaces of attacks.

An alternative exists, though, if you're using an API Gateway. I'll describe how to do it with Apache APISIX, but perhaps other gateways can do the same. grpc-transcode is a plugin that allows transcoding REST calls to gRPC and back again.

I've used Kong but currently evaluating APISix as it's a more 'free/open' API gateway.

In this article, we will show you how to create a custom connector for the open-source Apache APISIX API Gateway in Power Platform as an alternative to Azure API Management in case you are building up additional components to an existing system with usable APIs and your system's infrastructure is hosted on-premises or on other cloud services provider rather than Azure.

Here's how to do it with Apache APISIX.

Apache APISIX is an open-source, high-performance API gateway built on top of Nginx. One of its powerful features is the ability to create serverless functions, which are small, stateless programs that can extend the functionality of Apache APISIX. In this article, we'll cover the basics of the Apache APISIX serverless plugin and how it can be used to trigger serverless functions in response to events.