Why API gateways unify service access in Microservices - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary role of an API gateway in microservices?

An API gateway acts as a single entry point for clients to access multiple microservices. What is its main purpose?

A It replaces microservices by combining all their logic into one service.

B It stores all the data for microservices to reduce database load.

C It routes client requests to the appropriate microservice and handles cross-cutting concerns like authentication and rate limiting.

D It directly manages the deployment of microservices on servers.

💡 Hint

Think about how clients interact with many services through one point.

API gateways unify access by routing requests and managing common tasks like security and traffic control, simplifying client interactions.

❓ Architecture

intermediate

Which component best fits between clients and microservices to unify access?

You want to design a system where clients do not call microservices directly but through a unified layer. Which component should you place?

A Database Proxy

B API Gateway

C Load Balancer

D Service Registry

💡 Hint

This component handles routing and common client requests.

An API Gateway sits between clients and microservices to unify access, unlike load balancers or service registries which serve different purposes.

❓ scaling

advanced

How does an API gateway help scale microservices efficiently?

Consider a system with many microservices and clients. How does using an API gateway improve scalability?

A By storing all client data inside the gateway to avoid microservice calls.

B By duplicating all microservices inside the gateway to handle requests locally.

C By forcing clients to call each microservice separately to balance load.

D By centralizing request routing and caching, it reduces direct load on microservices and improves response times.

💡 Hint

Think about how centralizing common tasks can reduce repeated work.

API gateways can cache responses and route requests efficiently, reducing the number of calls microservices must handle directly.

❓ tradeoff

advanced

What is a potential downside of using an API gateway to unify service access?

While API gateways simplify client access, what is a common tradeoff to consider?

A It can become a single point of failure and add latency if not designed properly.

B It requires clients to know all microservice endpoints directly.

C It eliminates the need for microservices, causing monolithic design.

D It stores all application data, increasing database complexity.

💡 Hint

Think about risks of centralizing traffic through one component.

API gateways centralize traffic, so if they fail or are slow, the whole system can be affected.

❓ component

expert

In a microservices system with an API gateway, which feature is NOT typically handled by the gateway?

API gateways unify access and handle many tasks. Which of these is usually NOT a responsibility of the API gateway?

A Direct database transactions and complex business logic processing.

B Rate limiting and request throttling.

C Request routing to appropriate microservices.

D Authentication and authorization of client requests.

💡 Hint

Consider what tasks belong to microservices versus the gateway.

API gateways handle routing and security but do not perform core business logic or direct database operations.