2016-04-24 16:00:39 -05:00
|
|
|
---
|
|
|
|
|
layout: pattern
|
|
|
|
|
title: API Gateway
|
|
|
|
|
folder: api-gateway
|
|
|
|
|
permalink: /patterns/api-gateway/
|
2016-05-03 16:29:20 -05:00
|
|
|
categories: Architectural
|
2016-04-24 16:00:39 -05:00
|
|
|
tags:
|
|
|
|
|
- Java
|
2016-05-03 16:29:20 -05:00
|
|
|
- Difficulty-Intermediate
|
|
|
|
|
- Spring
|
2016-04-24 16:05:38 -05:00
|
|
|
---
|
2016-04-24 16:00:39 -05:00
|
|
|
|
|
|
|
|
## Intent
|
|
|
|
|
|
|
|
|
|
Aggregate calls to microservices in a single location: the API Gateway. The user makes a single
|
|
|
|
|
call to the API Gateway, and the API Gateway then calls each relevant microservice.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Applicability
|
|
|
|
|
|
|
|
|
|
Use the API Gateway pattern when
|
|
|
|
|
|
|
|
|
|
* you're also using the Microservices pattern and need a single point of aggregation for your
|
|
|
|
|
microservice calls
|
|
|
|
|
|
|
|
|
|
## Credits
|
|
|
|
|
|
|
|
|
|
* [microservices.io - API Gateway](http://microservices.io/patterns/apigateway.html)
|
|
|
|
|
* [NGINX - Building Microservices: Using an API Gateway](https://www.nginx.com/blog/building-microservices-using-an-api-gateway/)
|
