- 专注IT技术分享

首页 > Redis > redis 控制调用频率

redis 控制调用频率

时间:2016-08-28来源:网友分享 点击:

redis提供了rate limit demo 如下所示:

INCR key

Available since 1.0.0.

Time complexity: O(1)

Increments the number stored at key by one. If the key does not exist, it is set to 0 before performing the operation. An error is returned if the key contains a value of the wrong type or contains a string that can not be represented as integer. This operation is limited to 64 bit signed integers.

Note: this is a string operation because Redis does not have a dedicated integer type. The string stored at the key is interpreted as a base-10 64 bit signed integer to execute the operation.

Redis stores integers in their integer representation, so for string values that actually hold an integer, there is no overhead for storing the string representation of the integer.

Return value

: the value of key after the increment


redis> SET mykey "10"
redis> INCR mykey
(integer) 11
redis> GET mykey

Pattern: Counter

The counter pattern is the most obvious thing you can do with Redis atomic increment operations. The idea is simply send an  command to Redis every time an operation occurs. For instance in a web application we may want to know how many page views this user did every day of the year.

To do so the web application may simply increment a key every time the user performs a page view, creating the key name concatenating the User ID and a string representing the current date.

This simple pattern can be extended in many ways:

  • It is possible to use  and  together at every page view to have a counter counting only the latest N page views separated by less than the specified amount of seconds.
  • A client may use GETSET in order to atomically get the current counter value and reset it to zero.
  • Using other atomic increment/decrement commands like  or  it is possible to handle values that may get bigger or smaller depending on the operations performed by the user. Imagine for instance the score of different users in an online game.

Pattern: Rate limiter

The rate limiter pattern is a special counter that is used to limit the rate at which an operation can be performed. The classical materialization of this pattern involves limiting the number of requests that can be performed against a public API.

We provide two implementations of this pattern using , where we assume that the problem to solve is limiting the number of API calls to a maximum of ten requests per second per IP address.

Pattern: Rate limiter 1

The more simple and direct implementation of this pattern is the following:

FUNCTION LIMIT_API_CALL(ip)ts = CURRENT_UNIX_TIME()keyname = ip+":"+tscurrent = GET(keyname)IF current != NULL AND current > 10 THEN    ERROR "too many requests per second"ELSE    MULTI        INCR(keyname,1)        EXPIRE(keyname,10)    EXEC    PERFORM_API_CALL()END

Basically we have a counter for every IP, for every different second. But this counters are always incremented setting an expire of 10 seconds so that they'll be removed by Redis automatically when the current second is a different one.

Note the used of  and  in order to make sure that we'll both increment and set the expire at every API call.

Pattern: Rate limiter 2

An alternative implementation uses a single counter, but is a bit more complex to get it right without race conditions. We'll examine different variants.

FUNCTION LIMIT_API_CALL(ip):current = GET(ip)IF current != NULL AND current > 10 THEN    ERROR "too many requests per second"ELSE    value = INCR(ip)    IF value == 1 THEN        EXPIRE(value,1)    END    PERFORM_API_CALL()END

The counter is created in a way that it only will survive one second, starting from the first request performed in the current second. If there are more than 10 requests in the same second the counter will reach a value greater than 10, otherwise it will expire and start again from 0.

In the above code there is a race condition. If for some reason the client performs the  command but does not perform the  the key will be leaked until we'll see the same IP address again.

This can be fixed easily turning the  with optional  into a Lua script that is send using the  command (only available since Redis version 2.6).

local currentcurrent ="incr",KEYS[1])if tonumber(current) == 1 then"expire",KEYS[1],1)end

There is a different way to fix this issue without using scripting, but using Redis lists instead of counters. The implementation is more complex and uses more advanced features but has the advantage of remembering the IP addresses of the clients currently performing an API call, that may be useful or not depending on the application.

FUNCTION LIMIT_API_CALL(ip)current = LLEN(ip)IF current > 10 THEN    ERROR "too many requests per second"ELSE    IF EXISTS(ip) == FALSE        MULTI            RPUSH(ip,ip)            EXPIRE(ip,1)        EXEC    ELSE        RPUSHX(ip,ip)    END    PERFORM_API_CALL()END

The  command only pushes the element if the key already exists.

Note that we have a race here, but it is not a problem:  may return false but the key may be created by another client before we create it inside the  /  block. However this race will just miss an API call under rare conditions, so the rate limiting will still work correctly.

redis 控制调用频率

redis 控制调用频率   讨论

【redis,1】java操作redis: 将string、list、map、自定义的对象保存到redis中

一、操作string 、list 、map 对象 1、引入jar: jedis-2.1.0.jar2、代码 /** * @param args */ public static void main(String[]args){ //连接 redis 服务 Jedisjedis= new Jedis( ,6379); //密码验证-如果你没有设置 re...

【Redis 2】Redis数据库的学习与实践—redis的数据类型

Redis数据库的学习与实践—redis的数据类型 Redis 的数据类型: 1 : Strings 类型及操作: String 类型是最简单的类型,一个 Key 对应一个 Value , String 类型是二进制安全的。 Redis 的 String 可以包含...

redis sets类型及操作

sets类型及操作 set是集合,它是string类型的无序集合。通过hash table实现,添加、删除、查找的复杂度都是0(1)。对集合我们可以实现取交际、差集并集。通过这些操作我们可以实现SNS中的好友...

redis提供了rate limit demo 如下所示: INCR key Available since 1.0.0. Time complexity:O(1) Increments the number stored at key by one. If the key does not exist, it is set to 0 before performing the operation. An error is returned if the key