API Rate Limiting & Scalability Patterns · Lesson

Global vs. Per-Service Rate Limiting

Understand the differences and interplay between global rate limits applied at the edge and specific limits for individual microservices.

Global vs. Per-Service Rate Limiting is a free API Rate Limiting & Scalability Patterns lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the API Rate Limiting & Scalability Patterns learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

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.

Frequently asked questions

Is the “Global vs. Per-Service Rate Limiting” lesson free?

Yes — the full text of “Global vs. Per-Service Rate Limiting” is free to read here on the web, and the API Rate Limiting & Scalability Patterns course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the API Rate Limiting & Scalability Patterns course, upgrade to CoddyKit PRO.

What will I learn in “Global vs. Per-Service Rate Limiting”?

Understand the differences and interplay between global rate limits applied at the edge and specific limits for individual microservices. You practise API Rate Limiting & Scalability Patterns with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start API Rate Limiting & Scalability Patterns?

No prior experience is required. API Rate Limiting & Scalability Patterns on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Global vs. Per-Service Rate Limiting” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this API Rate Limiting & Scalability Patterns lesson?

Yes. Every API Rate Limiting & Scalability Patterns lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to API Rate Limiting & Scalability Patterns