API 게이트웨이 및 엣지 라우팅

In a microservices architecture, you might have many services. Clients (like your mobile app or web browser) need a single, clear way to interact with them.

An API Gateway acts as the front door for all external requests, routing them to the correct backend microservice.

• It's a single entry point.
• Simplifies client communication.
• Decouples clients from service details.

Edge routing refers to the process of directing incoming external network traffic to the appropriate internal destination.

The API Gateway typically embodies this edge routing function. It's the first component external requests hit, deciding where they should go next within your distributed system.

This is different from internal service-to-service communication, which might use a service mesh.

One of the core functions of an API Gateway is intelligent request routing. It examines incoming requests and forwards them to the relevant microservice.

Routing decisions can be based on:

• The URL path (e.g., /users goes to User Service).
• HTTP methods (GET, POST, PUT, DELETE).
• Request headers or query parameters.

This allows you to expose a clean, unified API to clients.

Here's a simplified Python concept of how an API Gateway might route a request based on its path. In a real system, this would involve network calls and complex logic.

API Gateways are excellent for centralizing security. Instead of each microservice handling its own authentication and authorization, the Gateway can do it once at the edge.

• It can validate API keys or JSON Web Tokens (JWTs).
• Ensure the user has permission for the requested action.
• This offloads security concerns from individual services.

To protect your backend services from being overwhelmed by too many requests (accidental or malicious), API Gateways can enforce rate limiting.

Rate limiting restricts the number of requests a user or client can make within a specific timeframe. For example, 100 requests per minute per IP address.

This helps maintain service availability and fairness.

Beyond routing and security, API Gateways offer more advanced features:

• Request/Response Transformation: Modify headers, body, or parameters.
• Caching: Store responses to reduce load on backend services.
• Logging & Monitoring: Centralize access logs and metrics.
• Circuit Breaking: Prevent cascading failures by isolating failing services.

These features enhance performance, reliability, and observability.

Adopting an API Gateway brings several key advantages to a microservices architecture:

• Simplified Client Code: Clients interact with one endpoint.
• Centralized Control: Manage cross-cutting concerns (security, logging) in one place.
• Improved Security: Enforce policies at the edge.
• Better Performance: Caching and efficient routing.
• Service Evolution: Backend services can change without affecting clients.

Many tools and services can act as API Gateways:

• Nginx/Envoy Proxy: Often used as a programmable proxy.
• Kong Gateway: An open-source, cloud-native API Gateway.
• AWS API Gateway: A fully managed service by Amazon.
• Spring Cloud Gateway: A framework for building API Gateways with Spring Boot.

The choice often depends on your cloud provider and technology stack.

An API Gateway is a crucial component in modern microservice architectures. It handles many cross-cutting concerns at the edge of your system.

Which of the following tasks are typically performed by an API Gateway?

You've learned about API Gateways and their vital role in distributed systems:

• They act as a single entry point for external clients.
• They perform intelligent request routing to microservices.
• They centralize authentication, authorization, and rate limiting.
• They can also offer features like caching, logging, and transformations.

API Gateways simplify client interactions and enhance the security and resilience of your microservices.