Gloo Routing

Gloo has a powerful routing engine that can handle simple use cases like API-to-API routing as well as more complex ones like HTTP to gRPC with body and header transformations. Gloo can also route natively to cloud-function providers like AWS Lambda, Google Cloud Functions and Azure Functions.

To understand Gloo routing, we should understand the high-level layout of the Gloo configuration. In general, you will be interacting with Virtual Services. These objects allow you to configure the details of the API you wish to expose on the Gateway as well as how the routing happens to any backends (Upstreams. To get traffic into the Gloo gateway, you need to control the listeners through the Gateway objects.

Structure of gateway configurations with virtual service

To configure the details of the routing engine, we define predicates that match on incoming requests (things like headers, path, method, etc) and then route them to Upstream destinations (like REST or gRPC services running in Kubernetes, EC2, Consul, etc or Cloud Functions like Lambda).

Structure of gateway configurations with virtual service

Take a look at getting started with the hello world guide and move to more advanced use cases by understanding the Virtual Service concept.