Gateway, Gateway, Gateway - What and for what?
The term “gateway” is used in the cloud environment for many different concepts: API Gateway, Ingress Gateway (Istio), and Kubernetes Gateway API (Kubernetes sig - special interest groups). All three terms have one thing in common. They create orderly and therefore controlled access to APIs. In addition to or in competition with this, the so-called ingress also (still) exists, with its associated ingress controller. With such an extensive selection of options, it is not easy to keep track of things. What is what and which “gateway” do we need in our environment? Is a single “gateway” enough for us or do we have to combine several “gateways”? How do we ensure that we don’t ride the wrong horse in the future? In order to be able to assess these questions better, the different gateway concepts will be presented in this session and, as far as possible, differentiated from each other. The possible areas of application for the gateways and the coexistence of several gateways, if this makes sense, are also discussed. At the end of the session, a look into the crystal ball will attempt to clear the fog of future developments in this area.