Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Latest commit

 

History

History
History
31 lines (23 loc) · 948 Bytes

File metadata and controls

31 lines (23 loc) · 948 Bytes
Copy raw file
Download raw file
Outline
Edit and raw actions
layout pattern
title API Gateway
folder api-gateway
permalink /patterns/api-gateway/
pumlid JSox3SCm303HLP819FRUXg49cO542_nOyFPncUvUSszHwhbpMdyT4TCt0CDLcyIHdtGsEZLOez8vG7ek33JuueLbPvUcPM84cpeCz2S0fvI6mGjluA1_b-Tt2N5D6tNcw3y0
categories Architectural
tags
Java
Difficulty-Intermediate
Spring

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.

alt text

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

Morty Proxy This is a proxified and sanitized view of the page, visit original site.