[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.] #  @itsr_kumar Ritik Kumar Ritik Kumar posts on X about redis, 100k, instead of the most. They currently have XXXXX followers and X posts still getting attention that total X engagements in the last XX hours. ### Engagements: undefined [#](/creator/twitter::1242490679021801472/interactions)  - X Year XX -XX% ### Mentions: undefined [#](/creator/twitter::1242490679021801472/posts_active)  - X Year XX +233% ### Followers: XXXXX [#](/creator/twitter::1242490679021801472/followers)  - X Year XXXXX -XXXX% ### CreatorRank: undefined [#](/creator/twitter::1242490679021801472/influencer_rank)  ### Social Influence [#](/creator/twitter::1242490679021801472/influence) --- **Social topic influence** [redis](/topic/redis) 62.5%, [100k](/topic/100k) 12.5%, [instead of](/topic/instead-of) XXXX% ### Top Social Posts [#](/creator/twitter::1242490679021801472/posts) --- Top posts by engagements in the last XX hours "Most of us start our system design journey with the classic rate limiter problem and realise how crucial it is to prevent our system against a DDoS attack. But what if therate limiter itselfbecomes the bottleneck under attack" [X Link](https://x.com/itsr_kumar/status/1983465326936539549) [@itsr_kumar](/creator/x/itsr_kumar) 2025-10-29T09:25Z 1240 followers, XX engagements "💠Picture this: We create a standard rate limiter: request extract user/IP hash check Redis quota allow or drop. Now were hit with 100000 requests/sec limit set to allow 10/sec. Wed think 99990 requests just get dropped" [X Link](https://x.com/itsr_kumar/status/1983465329172046179) [@itsr_kumar](/creator/x/itsr_kumar) 2025-10-29T09:26Z 1240 followers, XX engagements "⚡ But heres the catcheven with a Redis cluster sharding load were still processing all 100k requests slamming Redis anyway. If we can detect abuse in the first XX requests do we really want the next 99990 even touching the expensive infra" [X Link](https://x.com/itsr_kumar/status/1983465332212892040) [@itsr_kumar](/creator/x/itsr_kumar) 2025-10-29T09:26Z 1240 followers, XX engagements "Here are potential ways to tackle it: 🔷 Local Pre-filtering & Sampling: Early circuit-breaker logic at the load balancer or edge proxies. Before even checking Redis discard obvious abuse patterns (e.g. no valid auth bad IPs expired tokens)" [X Link](https://x.com/itsr_kumar/status/1983465334503010351) [@itsr_kumar](/creator/x/itsr_kumar) 2025-10-29T09:26Z 1240 followers, XX engagements "🔷 Hash-Based Batching: Instead of checking Redis for every request batch requests with the same rate limit keymaking a single counter increment for the entire batch or time window" [X Link](https://x.com/itsr_kumar/status/1983465336809963661) [@itsr_kumar](/creator/x/itsr_kumar) 2025-10-29T09:26Z 1240 followers, XX engagements "🔷 Graceful Fail-Closed: If Redis is overloaded or unreachable switch to a conservative mode: serve HTTP XXX (Too Many Requests) by default protecting the backend even if the limiter is hurting" [X Link](https://x.com/itsr_kumar/status/1983465343935975483) [@itsr_kumar](/creator/x/itsr_kumar) 2025-10-29T09:26Z 1240 followers, XX engagements
[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
@itsr_kumar Ritik Kumar
Ritik Kumar posts on X about redis, 100k, instead of the most. They currently have XXXXX followers and X posts still getting attention that total X engagements in the last XX hours.
Engagements: undefined #
- X Year XX -XX%
Mentions: undefined #
- X Year XX +233%
Followers: XXXXX #
- X Year XXXXX -XXXX%
CreatorRank: undefined #
Social Influence #
Social topic influence redis 62.5%, 100k 12.5%, instead of XXXX%
Top Social Posts #
Top posts by engagements in the last XX hours
"Most of us start our system design journey with the classic rate limiter problem and realise how crucial it is to prevent our system against a DDoS attack. But what if therate limiter itselfbecomes the bottleneck under attack"
X Link @itsr_kumar 2025-10-29T09:25Z 1240 followers, XX engagements
"💠Picture this: We create a standard rate limiter: request extract user/IP hash check Redis quota allow or drop. Now were hit with 100000 requests/sec limit set to allow 10/sec. Wed think 99990 requests just get dropped"
X Link @itsr_kumar 2025-10-29T09:26Z 1240 followers, XX engagements
"âš¡ But heres the catcheven with a Redis cluster sharding load were still processing all 100k requests slamming Redis anyway. If we can detect abuse in the first XX requests do we really want the next 99990 even touching the expensive infra"
X Link @itsr_kumar 2025-10-29T09:26Z 1240 followers, XX engagements
"Here are potential ways to tackle it: 🔷 Local Pre-filtering & Sampling: Early circuit-breaker logic at the load balancer or edge proxies. Before even checking Redis discard obvious abuse patterns (e.g. no valid auth bad IPs expired tokens)"
X Link @itsr_kumar 2025-10-29T09:26Z 1240 followers, XX engagements
"🔷 Hash-Based Batching: Instead of checking Redis for every request batch requests with the same rate limit keymaking a single counter increment for the entire batch or time window"
X Link @itsr_kumar 2025-10-29T09:26Z 1240 followers, XX engagements
"🔷 Graceful Fail-Closed: If Redis is overloaded or unreachable switch to a conservative mode: serve HTTP XXX (Too Many Requests) by default protecting the backend even if the limiter is hurting"
X Link @itsr_kumar 2025-10-29T09:26Z 1240 followers, XX engagements