Rate Limiting Not Enforced on API Endpoint
API has no rate limiting. Malicious users can spam endpoints with thousands of requests, causing DoS attack. Legitimate requests are throttled. API was designed but rate limiting was deferred as 'optimization' and never implemented.
No mechanism exists to slow down or reject excessive requests from single client.
Error Messages You Might See
Common Causes
- Rate limiting not implemented at all, feature deferred
- Rate limiting framework installed but not activated
- Rate limit too high, effectively no limit
- Limit applies globally instead of per-IP or per-user
- No storage of request counts (memory resets, limit doesn't persist)
How to Fix It
Implement rate limiting: library (spring-cloud-gateway, express-rate-limit) or custom middleware. Limit by IP: 100 requests per minute. Limit by user: 1000 per day. Store counts in Redis for persistence across restarts. Return 429 Too Many Requests when limit exceeded. Include Retry-After header indicating when to retry.
Real developers can help you.
Milan Surelia
Milan Surelia is a Mobile App Developer with 5+ years of experience crafting scalable, cross-platform apps at 7Span and Meticha. At 7Span, he engineers feature-rich Flutter apps with smooth performance and modern UI. As the Co-Founder of Meticha, he builds open-source tools and developer-focused products that solve real-world problems.
Expertise:
š” Developing cross-platform apps using Flutter, Dart, and Jetpack Compose for Android, iOS, and Web.
šļø Sharing insights through technical writing, blogging, and open-source contributions.
š¤ Collaborating closely with designers, PMs, and developers to build seamless mobile experiences.
Notable Achievements:
šÆ Revamped the Vepaar app into Vepaar Store & CRM with a 2x performance boost and smoother UX.
š Launched Compose101 ā a Jetpack Compose starter kit to speed up Android development.
š Open source contributions on Github & StackOverflow for Flutter & Dart
šļø Worked on improving app performance and user experience with smart solutions.
Milan is always happy to connect, work on new ideas, and explore the latest in technology.
BurnHavoc
Been around fixing other peoples code for 20 years.
MFox
Full-stack professional senior engineer (15+years). Extensive experience in software development, qa, and IP networking.
legrab
I'll fill this later
Bastien Labelle
Full stack dev w/ 20+ years of experience
Yovel Cohen
I got a lot of experience in building Long-horizon AI Agents in production, Backend apps that scale to millions of users and frontend knowledge as well.
Costea Adrian
Embedded Engineer specilizing in perception systems. Latest project was a adas camera calibration system.
Jen Jacobsen
Iām a Full-Stack Developer with over 10 years of experience building modern web and mobile applications. I enjoy working across the full product lifecycle ā turning ideas into real, well-built products that are intuitive for users and scalable for businesses.
I particularly enjoy building mobile apps, modern web platforms, and solving complex technical problems in a way that keeps systems clean, reliable, and easy to maintain.
PawelPloszaj
I'm fronted developer with 10+ years of experience with big projects. I have small backend background too
Simon A.
I'm a backend developer building APIs, emulators, and interactive game systems. Professionally, I've developed Java/Spring reporting solutions, managed relational and NoSQL databases, and implemented CI/CD workflows.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
What's a reasonable rate limit?
Public APIs: 100-1000 per hour per IP. Authenticated: 10000+ per hour per user. Adjust based on use cases.
How to implement with Redis?
Redis INCR + EXPIRE on keys like rate_limit:ip:192.168.1.1. Increment on each request, check if > limit.
Should rate limit reset?
Yes. Common: per minute, per hour, per day. Use EXPIRE in Redis: EXPIRE key 60 (expires after 60 seconds).