API Gateway
Services need one front door, so clients do not have to know every service behind it. The page first says what an API gateway is, then shows how NGINX can be the web server, reverse proxy, load balancer, and gateway at once.
The starting question is What is an API gateway? The archived javatpoint introduction answers it inside a microservices tutorial, next to topics such as load balancing and the Zuul gateway.
NGINX
With the gateway named, the practical question is what to run it on, and NGINX already covers most of the roles. NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers.
The term reverse proxy needs its own explanation, and Cloudflare on what is a reverse proxy is the proxy-servers explainer for it.
With both terms in hand, the NGINX blog makes the argument for not adding a separate product. From the NGINX blog:
One advantage of using NGINX as an API gateway is that it can perform that role while simultaneously acting as a reverse proxy, load balancer, and web server for existing HTTP traffic. If NGINX is already part of your application delivery stack then it is generally unnecessary to deploy a separate API gateway
Deprecated links
These links and images no longer work. The original wording is kept here. A same-resource copy, when one was checked, is used above.
what is. This address no longer opens: https://www.javatpoint.com/introduction-to-api-gateways
Last updated
Was this helpful?