Gloo is a feature-rich, Kubernetes-native ingress controller, and next-generation API gateway. Gloo is exceptional in its function-level routing; its support for legacy apps, microservices and serverless; its discovery capabilities; its numerous features; and its tight integration with leading open-source projects. Gloo is uniquely designed to support hybrid applications, in which multiple technologies, architectures, protocols, and clouds can coexist.
 
Gloo provides a long list of API gateway features, including rate limiting, circuit breaking, retries, caching, external authentication and authorization, transformation, service-mesh integration, and security.
 
Gloo can route requests directly to functions, which can be a serverless function call (e.g. Lambda, Google Cloud Function, OpenFaaS function, etc.), an API call on a microservice or a legacy service (e.g. a REST API call, OpenAPI operation, XML/SOAP request etc.), or publishing to a message queue (e.g. NATS, AMQP, etc.). This unique ability is what makes Gloo the only API gateway that supports hybrid apps, as well as the only one that does not tie the user to a specific paradigm.

Gloo is a feature-rich, Kubernetes-native ingress controller, and next-generation API gateway. Gloo is exceptional in its function-level routing; its support for legacy apps, microservices and serverless; its discovery capabilities; its numerous features; and its tight integration with leading open-source projects. Gloo is uniquely designed to support hybrid applications, in which multiple technologies, architectures, protocols, and clouds can coexist.

Gloo - The Function Gateway built on top of Envoy

Kong is a cloud-native, fast, scalable, and distributed Microservice Abstraction Layer (also known as an API Gateway, API Middleware or in some cases Service Mesh). Backed by the battle-tested NGINX with a focus on high performance, Kong was made available as an open-source platform in 2015. Under active development, Kong is used in production at thousands of organizations from startups, Global 5000 and Government organizations.
 
If you are building for web, mobile or IoT (Internet of Things) you will likely end up needing common functionality to run your actual software. Kong can help by acting as a gateway (or a sidecar) for microservices requests while providing load balancing, logging, authentication, rate-limiting and more through plugins.
 
Its features include: 
<ul>
<li>Cloud-Native: Platform agnostic, Kong can run from bare metal to
Kubernetes.</li>
<li>Dynamic Load Balancing: Load balance traffic across multiple backend
services.</li>
<li>Service Discovery: Resolve SRV records in third-party DNS resolvers like
Consul.</li>
<li>Serverless: Invoke and secure AWS Lambda or OpenWhisk fuctions directly
from Kong.</li>
<li>WebSockets: Communicate to your upstream services via WebSockets.</li>
<li>OAuth2.0: Easily add OAuth2.0 authentication to your APIs.</li>
<li>Logging: Log requests and responses to your system over HTTP, TCP, UDP,
or to disk.</li>
<li>Security: ACL, Bot detection, whitelist/blacklist IPs, etc...</li>
<li>Syslog: Logging to System log.</li>
<li>SSL: Setup a Specific SSL Certificate for an underlying service or API.</li>
<li>Monitoring: Live monitoring provides key load and performance server
metrics.</li>
<li>Authentications: HMAC, JWT, Basic, and more.</li>
<li>Rate-limiting: Block and throttle requests based on many variables.</li>
<li>Transformations: Add, remove, or manipulate HTTP requests and responses.</li>
<li>Caching: Cache and serve responses at the proxy layer.</li>
<li>CLI: Control your Kong cluster from the command line.</li>
<li>REST API: Kong can be operated with its RESTful API for maximum
flexibility.</li>
<li>Geo-Replicated: Configs are always up-to-date across different regions.</li>
<li>Failure Detection &amp; Recovery: Kong is unaffected if one of your Cassandra
nodes goes down.</li>
<li>Clustering: All Kong nodes auto-join the cluster keeping their config
updated across nodes.</li>
<li>Scalability: Distributed by nature, Kong scales horizontally by simply
adding nodes.</li>
<li>Performance: Kong handles load with ease by scaling and using NGINX at
the core.</li>
<li>Plugins: Extendable architecture for adding functionality to Kong and
APIs.</li>
</ul>

Kong is a cloud-native, fast, scalable, and distributed Microservice Abstraction Layer (also known as an API Gateway, API Middleware or in some cases Service Mesh). Backed by the battle-tested NGINX with a focus on high performance, Kong was made available as an open-source platform in 2015. Under active development, Kong is used in production at thousands of organizations from startups, Global 5000 and Government organizations.

Kong - The Microservice API Gateway 

Zuul is an edge service that provides dynamic routing, monitoring, resiliency, security, and more. Zuul is the front door for all requests from devices and web sites to the backend of the Netflix streaming application. As an edge service application, Zuul is built to enable dynamic routing, monitoring, resiliency and security. It also has the ability to route requests to multiple Amazon Auto Scaling Groups as appropriate.

Zuul - Gateway service that provides dynamic routing, monitoring, resiliency, security, and more

Apache APISIX is a dynamic, real-time, high-performance API gateway. APISIX provides rich traffic management features such as load balancing, dynamic upstream, canary release, circuit breaking, authentication, observability, and more. You can use Apache APISIX to handle traditional north-south traffic, as well as east-west traffic between services. It can also be used as a k8s ingress controller.
 
You can use Apache APISIX as a traffic entrance to process all business data, including dynamic routing, dynamic upstream, dynamic certificates, A/B testing, canary release, blue-green deployment, limit rate, defense against malicious attacks, metrics, monitoring alarms, service observability, service governance, etc.

Apache APISIX is a dynamic, real-time, high-performance API gateway. APISIX provides rich traffic management features such as load balancing, dynamic upstream, canary release, circuit breaking, authentication, observability, and more. You can use Apache APISIX to handle traditional north-south traffic, as well as east-west traffic between services. It can also be used as a k8s ingress controller.

Apache APISIX - Dynamic, real-time, high-performance API gateway

The apiman project brings an open source development methodology to API Management, coupling a rich API design & configuration layer with a blazingly fast runtime. It helps to govern your API. It is flexible, policy-based runtime governance for your APIs. Offer the same API through multiple plans, allowing different levels of service to different API consumers.
 
It provides rich management layer (REST API and separate UI) to manage/configure not only APIs but also the client applications that consume them. The runtime engine's API is fully asynchronous and is designed to run equally well in both a standard Java EE environment and newer async runtimes like Vert.x.

The apiman project brings an open source development methodology to API Management, coupling a rich API design & configuration layer with a blazingly fast runtime. It helps to govern your API. It is flexible, policy-based runtime governance for your APIs. Offer the same API through multiple plans, allowing different levels of service to different API consumers.

APIMAN - Open Source API Management

Resgate is a Go project implementing a realtime API gateway for the RES protocol with NATS server as messaging system. It is a simple server that lets you create REST, real time, and RPC APIs, where all your clients are synchronized seamlessly.
 
Resgate handles all API requests from your clients, instead of directly exposing your micro-services (represented by Node.js and Java below). Clients will connect to Resgate, using either HTTP or WebSocket, to make requests. These requests are sent to the micro-services over NATS server, and Resgate will keep track on which resource each client has requested. Whenever there is a change to the data, the responsible micro-service sends an event. Resgate will use this event to both update its own cache, and make sure each subscribing client is kept up-to-date.

Resgate is a Go project implementing a realtime API gateway for the RES protocol with NATS server as messaging system. It is a simple server that lets you create REST, real time, and RPC APIs, where all your clients are synchronized seamlessly.



Resgate - A Realtime API Gateway used with NATS to build REST, real time, and RPC APIs, where all your clients are synchronized seamlessly. 

Discover open source projects across all platforms

Projects

Gloo - The Function Gateway built on top of Envoy

Kong - The Microservice API Gateway

Zuul - Gateway service that provides dynamic routing, monitoring, resiliency, security, and more

Apache APISIX - Dynamic, real-time, high-performance API gateway

APIMAN - Open Source API Management

Resgate - A Realtime API Gateway used with NATS to build REST, real time, and RPC APIs, where all your clients are synchronized seamlessly.

TechStack

Tagcloud

License

Suggested keywords:

Projects

Gloo - The Function Gateway built on top of Envoy

Kong - The Microservice API Gateway

Zuul - Gateway service that provides dynamic routing, monitoring, resiliency, security, and more

Apache APISIX - Dynamic, real-time, high-performance API gateway

APIMAN - Open Source API Management

Resgate - A Realtime API Gateway used with NATS to build REST, real time, and RPC APIs, where all your clients are synchronized seamlessly.

TechStack

Tagcloud

License