Update website/content/docs/consul-vs-other/api-gateway-compare.mdx
Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>
This commit is contained in:
parent
7ac4fca0b9
commit
5bdfbf2c21
|
@ -9,7 +9,7 @@ description: >-
|
||||||
|
|
||||||
**Examples**: Kong Gateway, Apigee, Mulesoft, Gravitee
|
**Examples**: Kong Gateway, Apigee, Mulesoft, Gravitee
|
||||||
|
|
||||||
The Consul API Gateway ([documentation](/docs/api-gateway)) is an implementation of the [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/). Traditionally, API gateways are used for two things: _Client Traffic Management_ and _API Lifecycle Management_.
|
The [Consul API Gateway](/docs/api-gateway) is an implementation of the [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/). Traditionally, API gateways are used for two things: _Client Traffic Management_ and _API Lifecycle Management_.
|
||||||
|
|
||||||
Client traffic management refers to an API gateway's role in controlling the point of entry for public traffic into a given environment, also known as _managing north-south traffic_. The Consul API Gateway is deployed alongside Consul service mesh and is responsible for routing inbound client requests to the mesh based on defined routes. For a full list of supported traffic management features, refer to the [Consul API Gateway documentation](/docs/api-gateway).
|
Client traffic management refers to an API gateway's role in controlling the point of entry for public traffic into a given environment, also known as _managing north-south traffic_. The Consul API Gateway is deployed alongside Consul service mesh and is responsible for routing inbound client requests to the mesh based on defined routes. For a full list of supported traffic management features, refer to the [Consul API Gateway documentation](/docs/api-gateway).
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue