Two days ago, the API Gateway service on Oracle Cloud Infrastructure went live – read the announcement. This is a crucial component for many applications and in many solution designs. This new API Gateway is a prime candidate for example for inclusion in our reference architecture for OCI based solution designs. The API Gateway acts as a reverse proxy that handles HTTP requests from clients – either within OCI or on the public internet – and routes them to the configured endpoint. These endpoints can be any HTTP endpoint within OCI – such as Integration (OIC), an ingress on Kubernetes (OKE), a service in a Compute VM, ORDS on top of Autonomous Database – or outside of OCI. API Gateway also exposes Serverless Functions (Project Fn based) on OCI. One of the backend types supported by API Gateway – next to HTTP backend and Oracle Function as a backend – is Stock [response]; this type of backend always returns the exact same static response – headers and body. It can be used to quickly test [the health and availability and accessibility of) an API Gateway and a route (request policies are enforced in this case too) or to provide a mock response in stead of a backend that is still under development.
API Gateway lives in an OCI compartment, is associated with an OCI VCN and a public or private subnet. In case of the latter, the API Gateway is not publicly exposed and is used only for traffic within OCI. Read the complete article here.
For regular information become a member in the Developer Partner Community please register here.