Skip to content
Back to skills

Distributed Rate Limiting With Excel Configuration

ASecurity

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.

  • 581 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 30, 2026
educationspringkubernetesapibackend

Works with

  • api

Security analysis

A100/100

Scanned May 30, 2026

npx -y skills add ECNU-ICALK/AutoSkill --skill distributed-rate-limiting-with-excel-configuration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Distributed Rate Limiting With Excel Configuration?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Distributed Rate Limiting With Excel Configuration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ecnu-icalk-distributed-rate-limiting-with-excel-configuration/badge)](https://www.skillsdirectory.com/skills/ecnu-icalk-distributed-rate-limiting-with-excel-configuration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
id: "006cc2f7-93c5-4a72-92a1-08a3dd6f7204"
name: "Distributed Rate Limiting with Excel Configuration"
description: "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."
version: "0.1.0"
tags:
  - "rate limiting"
  - "redis"
  - "kubernetes"
  - "spring boot"
  - "distributed systems"
  - "excel configuration"
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"
---

# 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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.