Skip to content

Commit 4eecfaf

Browse files
authored
align API Gateway definition with CNCF Glossary (#3653)
* align API Gateway definition with CNCF Glossary * return header to previous level
1 parent 946c500 commit 4eecfaf

File tree

2 files changed

+25
-27
lines changed

2 files changed

+25
-27
lines changed

site-src/faq.md

Lines changed: 12 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -66,23 +66,22 @@ Guide](guides/tls.md) for more details about passthrough and other TLS
6666
configurations.
6767

6868
#### What's the difference between Gateway API and an API Gateway?
69-
An API Gateway is a general concept that describes anything that exposes
70-
capabilities of a backend service, while providing extra capabilities for
71-
traffic routing and manipulation, such as load balancing, request and response
72-
transformation, and sometimes more advanced features like authentication and
73-
authorization, rate limiting, and circuit breaking.
69+
An [API gateway](https://glossary.cncf.io/api-gateway/) is a tool that
70+
aggregates unique application APIs, making them all available in one place.
71+
It allows organizations to move key functions, such as authentication and
72+
authorization or limiting the number of requests between applications, to a
73+
centrally managed location. An API gateway functions as a common interface to (often external) API consumers.
7474

75-
Gateway API is an interface, or set of resources, that model service networking
76-
in Kubernetes. One of the main resources is a `Gateway`, which declares the
77-
Gateway type (or class) to instantiate and its configuration. As a Gateway
78-
Provider, you can implement Gateway API to model Kubernetes service networking
79-
in an expressive, extensible, and role-oriented way.
75+
Gateway API is an interface, defined as a set of Kubernetes resources, that
76+
models service networking in Kubernetes. One of the main resources is a `Gateway`,
77+
which declares the Gateway type (or class) to instantiate and its configuration.
78+
As a Gateway provider, you can implement Gateway API to model Kubernetes service
79+
networking in an expressive, extensible, and role-oriented way.
8080

81-
Most Gateway API implementations are API Gateways to some extent, but not all
82-
API Gateways are Gateway API implementations.
81+
Some API gateways can be programmed using the Gateway API.
8382

8483
#### Is Gateway API a standard for API Management?
8584
No. API Management is a much broader concept than what Gateway API aims to be,
8685
or what an API Gateway is intended to provide. An API Gateway can be an
8786
essential part of an API Management solution. Gateway API can be seen as a way
88-
to standardize on that aspect of API Management.
87+
to standardize provisioning of API Gateways.

site-src/index.md

Lines changed: 13 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -183,20 +183,19 @@ it must fit the uses to which each of Ana, Chihiro, and Ian will put it.
183183

184184
## What's the difference between Gateway API and an API Gateway?
185185

186-
An API Gateway is a general concept that describes anything that exposes
187-
capabilities of a backend service, while providing extra capabilities for
188-
traffic routing and manipulation, such as load balancing, request and response
189-
transformation, and sometimes more advanced features like authentication and
190-
authorization, rate limiting, and circuit breaking.
191-
192-
Gateway API is an interface, or set of resources, that model service
193-
networking in Kubernetes. One of the main resources is a `Gateway`, which
194-
declares the Gateway type (or class) to instantiate and its configuration. As
195-
a Gateway Provider, you can implement Gateway API to model Kubernetes
196-
service networking in an expressive, extensible, and role-oriented way.
197-
198-
Most Gateway API implementations are API Gateways to some extent, but not all
199-
API Gateways are Gateway API implementations.
186+
An [API gateway](https://glossary.cncf.io/api-gateway/) is a tool that
187+
aggregates unique application APIs, making them all available in one place.
188+
It allows organizations to move key functions, such as authentication and
189+
authorization or limiting the number of requests between applications, to a
190+
centrally managed location. An API gateway functions as a common interface to (often external) API consumers.
191+
192+
Gateway API is an interface, defined as a set of Kubernetes resources, that
193+
models service networking in Kubernetes. One of the main resources is a `Gateway`,
194+
which declares the Gateway type (or class) to instantiate and its configuration.
195+
As a Gateway provider, you can implement Gateway API to model Kubernetes service
196+
networking in an expressive, extensible, and role-oriented way.
197+
198+
Some API gateways can be programmed using the Gateway API.
200199

201200
## Who is working on Gateway API?
202201

0 commit comments

Comments
 (0)