0Pricing
API Rate Limiting & Scalability Patterns · Aula

Limitação de taxa global versus por serviço

Compreenda as diferenças e a interação entre limites de taxa globais aplicados na borda e limites específicos para microsserviços individuais.

Limitação de taxa global versus por serviço é uma aula grátis de API Rate Limiting & Scalability Patterns no CoddyKit. Esta é a aula 2 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de API Rate Limiting & Scalability Patterns, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de API Rate Limiting & Scalability Patterns inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

Global vs. Per-Service Limits

APIs often handle diverse traffic, from general users to specific internal systems. To manage this, we need different rate limiting strategies.

Today, we'll explore two key approaches: global rate limiting and per-service rate limiting. Understanding their differences helps build robust and fair APIs.

Guarding the Gates Globally

Global rate limiting is applied at the very edge of your system, before requests even reach individual services. Think of it as a bouncer at the club entrance.

  • It protects your entire infrastructure.
  • Often implemented in API Gateways, load balancers, or edge proxies.
  • Focuses on overall request volume to prevent system overload or DDoS attacks.

Global Limit Configuration

Here's a simplified example of how a global rate limit might be configured in an API Gateway like Nginx. It limits requests across all endpoints.

http {
  limit_req_zone $binary_remote_addr zone=mylimit:10m rate=10r/s;

  server {
    location / {
      limit_req zone=mylimit burst=20 nodelay;
      proxy_pass http://backend_services;
    }
  }
}

Why Global Limits Matter

Implementing global rate limits offers several advantages:

  • DDoS Protection: Blocks malicious traffic before it impacts your services.
  • Overall Stability: Ensures your entire system isn't overwhelmed by sudden traffic spikes.
  • Centralized Control: Easy to manage and modify limits for the whole API landscape.
  • Resource Efficiency: Less work for individual services to do for basic filtering.

Fine-Grained Service Control

Per-service rate limiting happens inside a specific microservice. It's like individual rules for different rooms within the club.

  • It applies to particular endpoints or operations within that service.
  • Implemented directly in the service's code or via a sidecar proxy.
  • Focuses on protecting specific service resources and enforcing business logic.

Per-Service Limit Code

Here's a tiny Java example illustrating a basic per-service rate limit for a specific endpoint. This uses a simple in-memory counter for demonstration.

import java.util.concurrent.ConcurrentHashMap;
import java.util.concurrent.atomic.AtomicInteger;
import java.time.Instant;

public class Main {
  private static final int MAX_REQUESTS_PER_MINUTE = 3;
  private static final long WINDOW_MILLIS = 60 * 1000; // 1 minute
  private static ConcurrentHashMap<String, Long> lastResetTime =
    new ConcurrentHashMap<>();
  private static ConcurrentHashMap<String, AtomicInteger> requestCounts =
    new ConcurrentHashMap<>();

  public static boolean allowRequest(String userId) {
    long currentTime = Instant.now().toEpochMilli();
    lastResetTime.computeIfAbsent(userId, k -> currentTime);
    requestCounts.computeIfAbsent(userId, k -> new AtomicInteger(0));

    // Reset if window passed
    if (currentTime - lastResetTime.get(userId) > WINDOW_MILLIS) {
      lastResetTime.put(userId, currentTime);
      requestCounts.get(userId).set(0);
    }

    if (requestCounts.get(userId).get() < MAX_REQUESTS_PER_MINUTE) {
      requestCounts.get(userId).incrementAndGet();
      return true;
    }
    return false;
  }

  public static void main(String[] args) {
    String userA = "user123";
    System.out.println("User A requests:");
    for (int i = 0; i < 5; i++) {
      System.out.println("Request " + (i + 1) + ": " +
        (allowRequest(userA) ? "Allowed" : "Denied"));
    }
    System.out.println("\nUser B requests:");
    String userB = "user456";
    for (int i = 0; i < 2; i++) {
      System.out.println("Request " + (i + 1) + ": " +
        (allowRequest(userB) ? "Allowed" : "Denied"));
    }
  }
}

Why Per-Service Limits are Key

Per-service rate limits provide more granular control:

  • Resource Protection: Prevents one endpoint from exhausting a service's specific resources (e.g., database connections).
  • Business Logic: Enforces limits based on specific user tiers or API functionality (e.g., "premium users get 1000 calls/min to this endpoint").
  • Isolation: A limit breach in one service doesn't necessarily bring down others.

Working Together: Layered Defense

The most robust systems use both global and per-service rate limits. They act as a layered defense:

  • Global limits: Act as a first line of defense, filtering out bulk traffic and protecting the entire system's entry point.
  • Per-service limits: Provide fine-tuned control within individual services, protecting specific resources and enforcing business rules.

Think of it as multiple checkpoints, each with a different purpose.

When to Use Which?

When designing your rate limiting strategy, consider:

  • Global: Best for broad protection, anonymous traffic, and preventing DDoS. Easy to implement at the infrastructure level.
  • Per-service: Ideal for protecting specific backend resources, enforcing user-specific quotas, or handling authenticated traffic with distinct access levels. Requires more application-level logic.

Often, a combination is the best approach.

Test Your Knowledge

Consider an API with a global rate limit of 1000 requests/second and a specific microservice endpoint that has a per-user limit of 10 requests/minute. A user makes 50 requests in 30 seconds to this specific endpoint.

Global vs. Per-Service Recap

We've explored the critical differences and synergy between global and per-service rate limiting:

  • Global limits: Act at the system's edge, protecting overall infrastructure from high-volume attacks.
  • Per-service limits: Provide fine-grained control within microservices, protecting specific resources and enforcing business rules.

Combining both strategies creates a robust, multi-layered defense for your APIs. Next, we'll dive into handling rate limit exceedance gracefully.

Perguntas Frequentes

A aula “Limitação de taxa global versus por serviço” é grátis?

Sim — o texto completo de “Limitação de taxa global versus por serviço” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de API Rate Limiting & Scalability Patterns, atualize para CoddyKit PRO. O curso de API Rate Limiting & Scalability Patterns inclui 4 aulas no total.

O que vou aprender em “Limitação de taxa global versus por serviço”?

Compreenda as diferenças e a interação entre limites de taxa globais aplicados na borda e limites específicos para microsserviços individuais. Você pratica API Rate Limiting & Scalability Patterns com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar API Rate Limiting & Scalability Patterns?

Nenhuma experiência prévia é necessária. API Rate Limiting & Scalability Patterns no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 4.

Quanto tempo leva a aula “Limitação de taxa global versus por serviço”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de API Rate Limiting & Scalability Patterns?

Sim. Cada aula de API Rate Limiting & Scalability Patterns inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Padrões de integração com gateways de API
  2. Limitação de taxa global versus por serviço
  3. Configuração dinâmica de limites de taxa
  4. Limitação distribuída de requisições com Redis
← Voltar para API Rate Limiting & Scalability Patterns