API 게이트웨이 통합 패턴

Welcome! In this lesson, we'll explore how API Gateways act as central traffic cops for your microservices, especially for rate limiting.

An API Gateway is a single entry point for all client requests to your backend services. It sits between clients and your microservices, handling requests before they reach individual services.

Implementing rate limiting at the API Gateway offers significant advantages over doing it in each microservice:

• Consistency: Ensures uniform rate limiting rules across all APIs.
• Simplicity: Simplifies microservice logic, as they don't need to handle rate limiting.
• Performance: Prevents overloaded services by rejecting excessive requests early.
• Visibility: Provides a single point for monitoring and auditing rate limit activity.

API Gateways enforce rate limits by intercepting incoming requests. They check each request against predefined rules before forwarding it to the target microservice.

These rules typically define a maximum number of requests allowed within a specific time window, often based on client IP, API key, or user ID.

Nginx is a popular open-source web server that can also function as a powerful API Gateway. It's known for its high performance and robust configuration options.

Nginx uses directives like limit_req_zone to define rate limiting parameters and limit_req to apply them to specific locations or routes.

Here's how you might configure Nginx to limit requests to 5 per second per IP address. The zone=mylimit:10m creates a 10MB shared memory zone for tracking, and rate=5r/s sets the limit.

Kong Gateway is another widely used open-source API Gateway built on Nginx. It's highly extensible through its plugin architecture, making it easy to add functionalities like rate limiting.

Kong offers a dedicated Rate Limiting plugin that can be applied globally, per service, per route, or even per consumer (API key).

For serverless and cloud-native architectures, AWS API Gateway provides built-in throttling capabilities. It allows you to set global limits, per-stage limits, and even client-specific limits using usage plans.

AWS API Gateway uses a token bucket algorithm to manage request rates and bursts, ensuring fair usage and protecting your backend services.

In AWS API Gateway, you typically configure rate limits via:

• Stage Throttling: Set default request rates and burst capacities for an entire deployment stage.
• Usage Plans: Create plans that define specific rate and burst limits for different groups of API consumers, often linked to API keys.

This allows fine-grained control over who can access your APIs and at what rate.

When implementing rate limiting at the API Gateway:

• Apply Early: Block requests as close to the client as possible to save backend resources.
• Granular Limits: Use different limits for different API endpoints or client tiers.
• Clear Responses: Provide informative error messages (e.g., HTTP 429 Too Many Requests) and Retry-After headers.
• Monitor: Continuously monitor rate limit metrics to identify potential bottlenecks or abuse patterns.

Which of the following are key benefits of implementing rate limiting at an API Gateway?

We've learned that API Gateways are crucial for centralizing cross-cutting concerns like rate limiting in microservices architectures.

By leveraging tools like Nginx, Kong, or AWS API Gateway, you can enforce consistent, efficient, and scalable rate limits, protecting your services and ensuring fair resource usage.