API gateway deployment models
The API gateway provides a facade pattern that encapsulates the inner workings of the system providing a single point of entry for all incoming clients. An API gateway can provide an API tailored for each type of client, all the while addressing concerns such as security, authentication, authorization, throttling, load balancing, and so on.
Let's look at the factors that impact how the APIs are deployed on the API gateway.
- Type of client or channel: Depending upon the device or channel from where the request originates, the API might need to serve different subsets of data. For example, the desktop version of the service might be asking for more details as compared to the mobile client. There can be a difference in data even between phone and tablet. How do we make sure that the same microservice can service all device type requests and still handle these variations? In this case, we create multiple APIs for different device types that meet the specific needs...
