An API gateway is essential part of organizing requests that need to be processed by different microservices.
The API Gateway handles all requests and then invokes the appropriate microservices and potentially aggregates the results; it is responsible for communicating between web protocols and the protocols being used by the various applications. For example, AWS’ API Gateway can handle converting requests from text into JSON.
API Gateway is a service that allows us to allow entry into our application from the outside world. The API Gateway is the single-entry point for our defined backend APIs and the microservices whether they are internal or external. It’s primary job is to protect, enforce security, and ensure scalability.
4 responses to “Introduction to API Gateway”
[…] system is responding to their request especially if it’s behind an API Gateway. See blog post Introduction to API Gateway for more details about how API Gateways […]
[…] and arguably one of the easiest to implement for the web. If you are using an API Gateway (Introduction to API Gateway ) it may not require any code […]
[…] Microservices are most often see when working with an API and are usually hidden behind an API Gateway. They should be small independently deployable services that have their own database, their own […]
[…] Read more about API Gateways in the blog post Introduction to API Gateway […]