doytsujin / gloo

The Feature-rich, Kubernetes-native, Next-Generation API Gateway Built on Envoy

An Envoy-Powered API Gateway

Gloo Edge is a feature-rich, Kubernetes-native ingress controller, and next-generation API gateway. Gloo Edge 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 Edge is uniquely designed to support hybrid applications, in which multiple technologies, architectures, protocols, and clouds can coexist.

Installation   |   Documentation   |   Blog   |   Slack   |   Twitter |   Enterprise Trial

Summary

• Using Gloo Edge
• What makes Gloo Edge unique

Using Gloo Edge

• Kubernetes ingress controller: Gloo Edge can function as a feature-rich ingress controller, built on top of the Envoy Proxy.
• Next-generation API gateway : Gloo Edge 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.
• Hybrid apps: Gloo Edge creates applications that route to backends implemented as microservices, serverless functions, and legacy apps. This feature can help users to gradually migrate from their legacy code to microservices and serverless; can let users add new functionalities using cloud-native technologies while maintaining their legacy codebase; can be used in cases where different teams in an organization choose different architectures; and more. See here for more on the Hybrid App paradigm.

What makes Gloo Edge unique

• Function-level routing allows integration of legacy applications, microservices and serverless: Gloo Edge 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 Edge 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 Edge incorporates vetted open-source projects to provide broad functionality: Gloo Edge support high-quality features by integrating with top open-source projects, including gRPC, GraphQL, OpenTracing, NATS and more. Gloo Edge's architecture allows rapid integration of future popular open-source projects as they emerge.
• Full automated discovery lets users move fast: Upon launch, Gloo Edge creates a catalog of all available destinations, and continuously maintains it up to date. This takes the responsibility for 'bookkeeping' away from the developers, and guarantees that new feature become available as soon as they are ready. Gloo Edge discovers across IaaS, PaaS and FaaS providers, as well as Swagger, gRPC, and GraphQL.
• Gloo Edge integrates intimately with the user's environment: with Gloo Edge, users are free to choose their favorite tools for scheduling (such as K8s, Nomad, OpenShift, etc), persistence (K8s, Consul, etcd, etc) and security (K8s, Vault).

Next Steps

• Join us on our Slack channel: https://slack.solo.io/
• Follow us on Twitter: https://twitter.com/soloio_inc
• Check out the docs: https://gloo.solo.io
• Check out the code and contribute: Contribution Guide
• Contribute to the Docs

Thanks

Gloo Edge would not be possible without the valuable open-source work of projects in the community. We would like to extend a special thank-you to Envoy.

Security

Reporting security issues: We take Gloo Edge's security very seriously. If you've found a security issue or a potential security issue in Gloo Edge, please DO NOT file a public Github issue, instead send your report privately to [email protected].