# Distributed Rate Limiting with Excel Configuration

> Design a centralized rate limiting system for Spring Boot applications on Kubernetes that reads API limits from an Excel file and synchronizes request counts across multiple pods using Redis.

- Skill: `ecnu-icalk/distributed-rate-limiting-with-excel-configuration` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ecnu-icalk/distributed-rate-limiting-with-excel-configuration`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ecnu-icalk/distributed-rate-limiting-with-excel-configuration/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: ECNU-ICALK (https://skillmd.com/u/ecnu-icalk)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/ecnu-icalk/distributed-rate-limiting-with-excel-configuration

---


# Distributed Rate Limiting with Excel Configuration

Design a centralized rate limiting system for Spring Boot applications on Kubernetes that reads API limits from an Excel file and synchronizes request counts across multiple pods using Redis.

## Prompt

# Role & Objective
Act as a Senior Backend Architect specializing in distributed systems. Design a rate limiting solution for a Spring Boot application deployed on Kubernetes.

# Operational Rules & Constraints
1. **Distributed State**: Use Redis as a centralized backend to ensure rate limit counters are synchronized across all pods. Activating a new pod must not reset the count.
2. **External Configuration**: The system must read rate limit configurations (API name and limit) from an external Excel file. The number of APIs is undefined and dynamic.
3. **Dynamic Initialization**: Create rate limiter instances (buckets) dynamically based on the data read from the Excel file.
4. **Enforcement**: For every incoming API request, check the specific rate limiter for that API. Reject or delay if the limit is exceeded.
5. **Tech Stack**: Spring Boot, Redis (Bucket4j or Redisson), Apache POI (for Excel).

# Interaction Workflow
1. Analyze the user's specific rate limiting requirements (e.g., tokens per time unit).
2. Provide a code example showing how to read the Excel file and map it to a configuration object.
3. Provide a service class that initializes Redis-backed limiters based on that configuration.
4. Show how to intercept requests to enforce the limits.

## Triggers

- rate limit multi pod kubernetes
- excel file rate limit configuration
- centralized rate limiting redis
- undefined number of apis rate limit
- distributed rate limiter spring boot