Rate Limiting with Redis

  Рет қаралды 32,707

Redis

Redis

Күн бұрын

Пікірлер
@immanuelbenhefer3437
@immanuelbenhefer3437 4 жыл бұрын
audio issues between 22:20 - 23:15
@user-qi5kb5th7y
@user-qi5kb5th7y Жыл бұрын
I think at 14:31 it would be more correct to set expire to: (86400 - math.floor(time.time()) % 86400) + 1 Because if the user has not used the API throughout the day, but uses it the last second of the day, the key will remain in the database for another day, since expire is set to this period.
@OmarQunsul
@OmarQunsul 3 жыл бұрын
On slide 15:25, why did you read the value after you issued (incrby) ? Because incrby already returns the new value
@ChrisAthanas
@ChrisAthanas Жыл бұрын
Same question
@subhajitghosh5911
@subhajitghosh5911 3 жыл бұрын
Thanks for the explanation. First method seems to be the fixed window approach and the second one is specifically the Sliding Window Log method.
@HarshaTALLAM-fo4em
@HarshaTALLAM-fo4em Жыл бұрын
In the second approach, when you are setting expiry for each record for a day, Why do you have to again actively remove keys that are older than 1 day using zremrangebyscore ?
@atabhatti6010
@atabhatti6010 2 жыл бұрын
Excellent presentation with lots of good detail. Walking through the code examples is awesome. Thanks! Unfortunately the audio is garbled for several minutes and I wonder if I am missing out on some good content. Can you please fix and repost?
@rudrapal2586
@rudrapal2586 4 жыл бұрын
Good explanation. Extremely helpful.
@ChrisAthanas
@ChrisAthanas Жыл бұрын
22:39 audio issues make it unlistenable Please remake this video
@mukhiddinkhalimetov8297
@mukhiddinkhalimetov8297 3 жыл бұрын
Second method can be done in more easier way. Simply, store epoch time in the value (if does not exists). In each request, increment it for some number (this number relates to the "window" lenght). Set the expiration to the value. Check difference between the value and current epoch time (this determines number of requests during the window)
@user-qi5kb5th7y
@user-qi5kb5th7y Жыл бұрын
i think your approach cannot be done atomically, so it might be subject to race conditions
@uppermiddleclass
@uppermiddleclass 3 жыл бұрын
Thank you very much for this insightful video! Is my understanding correct that zadd call actually increase memory footprint of the particular sortedset instance inside of the Redis instance? We do this for every API call being evaluated - so, if I understand correctly, memory footprint of Redis instance linearly depends on API call number . Could this be used to attack our system and if so how to configure Redis to prevent this?
@Redisinc
@Redisinc 3 жыл бұрын
Really glad you liked it! We are working to bring a lot more content to our KZbin very soon! subscriber here, or jump into our discord channel to chat with active Redis users who can answer your questions! Join our Discord server → discord.gg/redis
@yoka791
@yoka791 3 жыл бұрын
why the key should contain the timestamp of the start of day? Isn't that possible to save the key without the timestamp and rely on the ttl by setting it only when no record exist (=first request in a time windows of a day)?
@360Legion
@360Legion 2 жыл бұрын
I believe that is the good approach .. although as a gate keeping mechanism, its better to remove the key if it is longer than 24 hours as well.
@SoloistKavin
@SoloistKavin 3 жыл бұрын
the second approach uses sorted sets... isnt that expensive... can we not use hyperloglog without being too expensive... imagine a uses case where there is spike in traffic and there is a large sorted set that needs to be read for every request?
@SunnyGuptaTech
@SunnyGuptaTech 4 жыл бұрын
Nice explanation 👍
@polskieyt9191
@polskieyt9191 2 жыл бұрын
#cool
@Redisinc
@Redisinc 2 жыл бұрын
😎
@greendsnow
@greendsnow Жыл бұрын
Upstash is making a lot of money off of devs who CAN'T setup up a rate limiter with your product... What more should I say... And here, you guys have come up with a code that is in python... poor choices...
@Redisinc
@Redisinc 11 ай бұрын
Thank for the feedback!
What is Rate Limiting / API Throttling? | System Design Concepts
16:11
Be A Better Dev
Рет қаралды 68 М.
It works #beatbox #tiktok
00:34
BeatboxJCOP
Рет қаралды 41 МЛН
Quando A Diferença De Altura É Muito Grande 😲😂
00:12
Mari Maria
Рет қаралды 45 МЛН
5 Redis Use Cases with Gur Dotan - Redis Labs
10:14
Redis
Рет қаралды 47 М.
Why Your MySQL Needs Redis
58:20
Redis
Рет қаралды 63 М.
Scaling Push Messaging for Millions of Devices @Netflix
49:10
Redis Data Structures for Non-Redis Users
48:00
Redis
Рет қаралды 28 М.
Rate limiting with Redis: An essential guide
5:42
Redis
Рет қаралды 287
System Design Interview - Rate Limiting (local and distributed)
34:36
System Design Interview
Рет қаралды 307 М.
Distributed Systems in One Lesson by Tim Berglund
49:00
Devoxx Poland
Рет қаралды 418 М.
Rate Limiting system design | TOKEN BUCKET, Leaky Bucket, Sliding Logs
35:55
Tech Dummies Narendra L
Рет қаралды 287 М.
It works #beatbox #tiktok
00:34
BeatboxJCOP
Рет қаралды 41 МЛН