Why API Gateway pattern in Microservices? - Purpose & Use Cases

The Big Idea

What if one simple door could open access to all your favorite shops without the hassle?

The Scenario

Imagine you have many small shops in a market, and customers must visit each shop separately to buy what they want. They carry many bags and spend a lot of time walking around.

The Problem

Without a central helper, customers get confused, waste time, and sometimes miss shops. Shops struggle to manage many separate requests, leading to slow service and mistakes.

The Solution

The API Gateway acts like a friendly market guide who knows all shops. Customers talk to the guide once, and the guide fetches everything from the shops, making shopping fast and easy.

Before vs After

✗ Before

client.call(serviceA)
client.call(serviceB)
client.call(serviceC)

✓ After

client.call(apiGateway)

What It Enables

It enables a simple, unified entry point that hides complexity and improves performance and security for many services.

Real Life Example

Think of a food delivery app where you order from many restaurants but only interact with one app that handles all orders smoothly behind the scenes.

Key Takeaways

API Gateway simplifies client interactions by providing one access point.

It improves system scalability, security, and maintenance.

It hides the complexity of multiple backend services from users.

Practice

1. What is the primary role of an API Gateway in a microservices architecture?

easy

A. It acts as a single entry point to route requests to multiple microservices.

B. It stores all the data for the microservices.

C. It replaces the database in the system.

D. It directly manages the internal logic of each microservice.

Solution

1. Step 1: Understand the role of API Gateway

   An API Gateway serves as a single entry point that routes client requests to the appropriate microservices.

2. Step 2: Eliminate incorrect roles

   It does not store data, replace databases, or manage internal microservice logic; those are handled by other components.

3. Final Answer:

   It acts as a single entry point to route requests to multiple microservices. -> Option A

4. Quick Check:

   API Gateway = Single entry point [OK]

Hint: API Gateway routes requests, it does not store data [OK]

Common Mistakes:

• Confusing API Gateway with database or service logic
• Thinking API Gateway manages microservice internals
• Assuming API Gateway stores data

2. Which of the following is the correct way to describe the API Gateway's function in handling client requests?

easy

A. API Gateway directly executes business logic for each microservice.

B. API Gateway replaces the need for microservices.

C. API Gateway stores client data permanently.

D. API Gateway routes requests, handles authentication, and aggregates responses.

Solution

1. Step 1: Identify API Gateway responsibilities

   API Gateway routes requests, manages security like authentication, and can combine responses from multiple services.

2. Step 2: Remove incorrect options

   It does not execute business logic itself, store data permanently, or replace microservices.

3. Final Answer:

   API Gateway routes requests, handles authentication, and aggregates responses. -> Option D

4. Quick Check:

   Routing + Security + Aggregation = API Gateway [OK]

Hint: API Gateway routes and secures, does not store data [OK]

Common Mistakes:

• Thinking API Gateway runs business logic
• Confusing API Gateway with data storage
• Assuming API Gateway replaces microservices

3. Consider this simplified request flow: A client sends a request to the API Gateway, which then calls Service A and Service B. The API Gateway combines their responses and sends back a single response to the client. What is the main benefit of this approach?

medium

A. It increases the number of client requests to microservices.

B. It reduces the number of client requests by aggregating responses.

C. It forces clients to call each microservice separately.

D. It eliminates the need for microservices.

Solution

1. Step 1: Analyze the request flow

   The API Gateway receives one client request and internally calls multiple services, then combines their responses.

2. Step 2: Understand the benefit

   This reduces the number of requests the client must make, simplifying client logic and improving efficiency.

3. Final Answer:

   It reduces the number of client requests by aggregating responses. -> Option B

4. Quick Check:

   Response aggregation reduces client calls [OK]

Hint: API Gateway aggregates responses to reduce client calls [OK]

Common Mistakes:

• Thinking client must call each service separately
• Believing API Gateway increases client requests
• Confusing aggregation with service removal

4. A developer implemented an API Gateway but notices that clients receive errors when calling multiple microservices through it. Which of the following is the most likely cause?

medium

A. The client is bypassing the API Gateway and calling microservices directly.

B. The microservices do not have any APIs.

C. The API Gateway is not properly routing requests to the correct microservices.

D. The API Gateway is storing all client data incorrectly.

Solution

1. Step 1: Identify the error source

   If clients get errors when calling multiple services via the API Gateway, routing issues are a common cause.

2. Step 2: Exclude other causes

   Microservices usually have APIs; clients bypassing the gateway would not cause errors through it; storing data is not the gateway's role.

3. Final Answer:

   The API Gateway is not properly routing requests to the correct microservices. -> Option C

4. Quick Check:

   Routing errors cause client failures [OK]

Hint: Check routing rules if clients get errors via API Gateway [OK]

Common Mistakes:

• Blaming microservices for missing APIs
• Assuming clients bypass the gateway
• Thinking API Gateway stores client data

5. You are designing a system with multiple microservices and want to use an API Gateway. Which of the following is the best reason to include response aggregation in the API Gateway?

hard

A. To reduce client complexity by combining data from multiple services into one response.

B. To increase the number of network calls clients must make.

C. To allow clients to manage authentication for each microservice separately.

D. To store all microservice data centrally in the API Gateway.

Solution

1. Step 1: Understand response aggregation purpose

   Response aggregation combines data from multiple microservices into a single response, simplifying client handling.

2. Step 2: Evaluate other options

   Increasing network calls or forcing clients to manage authentication per service adds complexity; storing data centrally is not the gateway's role.

3. Final Answer:

   To reduce client complexity by combining data from multiple services into one response. -> Option A

4. Quick Check:

   Aggregation simplifies client responses [OK]

Hint: Aggregate responses to simplify client communication [OK]

Common Mistakes:

• Thinking aggregation increases client calls
• Assuming clients handle all authentications
• Confusing API Gateway with data storage