skills.rest
taipt1504
taipt1504COMMUNITY
Explore all skills by this author →
GitHub

summer-ratelimit

Apply Summer Framework rate-limiting policies with Redis or in-memory storage.

3|2|Updated Jan 16, 2026
Search Tags:#multi-tenant#redis#rate-limiting#per-user#policy-based#summer-framework#per-ip
One-click install
npx skills add https://github.com/taipt1504/agent-skills --skill summer-ratelimit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: summer-ratelimit
Source: https://github.com/taipt1504/agent-skills/tree/main/skills/summer-ratelimit
Command: npx skills add https://github.com/taipt1504/agent-skills --skill summer-ratelimit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Efficiently enforce rate limits across Summer Framework projects, preventing abuse and protecting services from bursts.

Core Features & Use Cases

  • Three strategies: fixed-window, sliding-window, and token-bucket, with Redis or in-memory storage.
  • Policy-driven scopes: per-user, per-IP, per-tenant, or global limits, with auto-429 support via acquire().
  • Observability & integration: easy configuration, Lua-script-backed atomicity, and monitoring hooks.

Quick Start

Install and configure per-scope rate-limit policies in your Summer-based Spring project to enforce API throttling.

Frequently Asked Questions about summer-ratelimit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce rate limits in a microservices architecture using Redis?▼

You can enforce rate limits in microservices by applying policy-driven scopes with Redis-backed storage. This approach supports per-user, per-IP, per-tenant, or global limits to prevent API abuse across distributed services.

What rate limiting strategies are available for the Summer Framework?▼

The Summer Framework supports three rate limiting strategies: fixed-window, sliding-window, and token-bucket. Each strategy can utilize Redis-backed or in-memory storage to apply policy-driven API throttling.

Can I apply per-tenant API throttling policies across multiple scopes?▼

Yes, you can apply per-tenant API throttling alongside per-user, per-IP, or global scopes. Policy-driven defaults allow flexible configuration to limit API usage based on specific tenant requirements.

How do I configure rate limits to automatically return a 429 status code?▼

To automatically return a 429 status code, use the acquire() method within your rate-limiting configuration. This method enforces policy-driven limits and triggers the auto-429 response when the threshold is exceeded.

Does Summer rate limiting use Lua scripts for atomic operations in Redis?▼

Yes, Summer rate limiting uses Lua-script-backed atomicity for Redis storage. This ensures safe concurrent operations when applying fixed-window, sliding-window, or token-bucket strategies across distributed environments.

What are the limitations of using in-memory storage for rate limiting?▼

In-memory storage for rate limiting is limited to single-instance deployments and cannot share state across microservices. For distributed environments, Redis-backed storage is required to maintain accurate per-tenant or global thresholds.

Related Skills

Explore More Software Engineering Skills→
taipt1504taipt1504
3

summer-security

Integrate APISIX X-Userinfo decoding and Keycloak role synchronization with Spring Security.

Community
Advanced
aiappsgbbaiappsgbb
5

apim_throttle_expert

Classifies 429 root causes in Husky's Astro API Gateway from routing metadata.

Official
Intermediate
shafibabarshafibabar
1

api-gateway-design

Design north-south API gateway architecture for edge policy enforcement.

Community
Advanced
balsm-healthbalsm-health
2

implementing-api-rate-limiting-and-throttling

Implement API rate limiting and throttling with token bucket, sliding window, and fixed window algorithms.

Official
Advanced