


Introduction to redis counter method to prevent brushing orders
If we want to handle concurrency limits on interface requests, or make a security interception to prevent order fraud, for example, for an interface request, limit the total number of requests per second to 200, and wait if the number exceeds 200. One second, request again, here a redis is used as a counter mode to implement. This article mainly introduces to you the method and related code of redis to implement counter to prevent fraudulent orders. It has certain reference value and friends in need can learn about it.
Method to call redis:
INCR key
Increase the numerical value stored in key by one.
If key does not exist, the value of key will be initialized to 0 first, and then the INCR operation will be performed.
If the value contains the wrong type, or a string type value cannot be represented as a number, then an error is returned.
This is an operation for strings. Because Redis does not have a dedicated integer type, the string stored in the key is interpreted as a decimal 64-bit signed integer to perform the INCR operation.
code:
redis> SET test 20 OK redis> INCR test (integer) 21 redis> GET test # 数字值在 Redis 中以字符串的形式保存 "21"
Implementation of counter
The counter is the atomic increment of Redis The most intuitive pattern that operations can implement, the idea is quite simple: every time an operation occurs, send an INCR command to Redis.
For example, in a web application, if you want to know the number of user clicks every day for a year, then you only need to use the user ID and related date information as keys, and execute it every time the user clicks on the page. One auto-increment operation is enough.
For example, if the user name is peter and the click time is March 22, 2012, then execute the command INCR peter::2012.3.22.
$redisKey = “api_name_” + $api; $count = $this->redis->incr($redisKey); if ($count == 1) { //设置有效期一s $this->redis->expire($redisKey,1);//设置一s的过期时间 } if (count > 200) {//防止刷单的安全拦截 return false;//超过就返回false } //后续处理
This simply implements the application of redis counter, and there are also the following methods:
The following are There are several ways to extend this simple pattern:
You can use INCR and EXPIRE in combination to achieve the purpose of counting only within the specified lifetime.
The client can atomically obtain the current value of the counter and clear the counter by using the GETSET command. For more information, please refer to the GETSET command.
Using other increment/decrement operations, such as DECR and INCRBY, users can increase or decrease the value of the counter by performing different operations. For example, these commands may be used for scorers in games.
Related recommendations:
Summary of usage of Redis function in php
Full record of Redis cluster construction
10 recommended content for performance counters
The above is the detailed content of Introduction to redis counter method to prevent brushing orders. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











Redis cluster mode deploys Redis instances to multiple servers through sharding, improving scalability and availability. The construction steps are as follows: Create odd Redis instances with different ports; Create 3 sentinel instances, monitor Redis instances and failover; configure sentinel configuration files, add monitoring Redis instance information and failover settings; configure Redis instance configuration files, enable cluster mode and specify the cluster information file path; create nodes.conf file, containing information of each Redis instance; start the cluster, execute the create command to create a cluster and specify the number of replicas; log in to the cluster to execute the CLUSTER INFO command to verify the cluster status; make

How to clear Redis data: Use the FLUSHALL command to clear all key values. Use the FLUSHDB command to clear the key value of the currently selected database. Use SELECT to switch databases, and then use FLUSHDB to clear multiple databases. Use the DEL command to delete a specific key. Use the redis-cli tool to clear the data.

To read a queue from Redis, you need to get the queue name, read the elements using the LPOP command, and process the empty queue. The specific steps are as follows: Get the queue name: name it with the prefix of "queue:" such as "queue:my-queue". Use the LPOP command: Eject the element from the head of the queue and return its value, such as LPOP queue:my-queue. Processing empty queues: If the queue is empty, LPOP returns nil, and you can check whether the queue exists before reading the element.

On CentOS systems, you can limit the execution time of Lua scripts by modifying Redis configuration files or using Redis commands to prevent malicious scripts from consuming too much resources. Method 1: Modify the Redis configuration file and locate the Redis configuration file: The Redis configuration file is usually located in /etc/redis/redis.conf. Edit configuration file: Open the configuration file using a text editor (such as vi or nano): sudovi/etc/redis/redis.conf Set the Lua script execution time limit: Add or modify the following lines in the configuration file to set the maximum execution time of the Lua script (unit: milliseconds)

Use the Redis command line tool (redis-cli) to manage and operate Redis through the following steps: Connect to the server, specify the address and port. Send commands to the server using the command name and parameters. Use the HELP command to view help information for a specific command. Use the QUIT command to exit the command line tool.

Redis counter is a mechanism that uses Redis key-value pair storage to implement counting operations, including the following steps: creating counter keys, increasing counts, decreasing counts, resetting counts, and obtaining counts. The advantages of Redis counters include fast speed, high concurrency, durability and simplicity and ease of use. It can be used in scenarios such as user access counting, real-time metric tracking, game scores and rankings, and order processing counting.

There are two types of Redis data expiration strategies: periodic deletion: periodic scan to delete the expired key, which can be set through expired-time-cap-remove-count and expired-time-cap-remove-delay parameters. Lazy Deletion: Check for deletion expired keys only when keys are read or written. They can be set through lazyfree-lazy-eviction, lazyfree-lazy-expire, lazyfree-lazy-user-del parameters.

In Debian systems, readdir system calls are used to read directory contents. If its performance is not good, try the following optimization strategy: Simplify the number of directory files: Split large directories into multiple small directories as much as possible, reducing the number of items processed per readdir call. Enable directory content caching: build a cache mechanism, update the cache regularly or when directory content changes, and reduce frequent calls to readdir. Memory caches (such as Memcached or Redis) or local caches (such as files or databases) can be considered. Adopt efficient data structure: If you implement directory traversal by yourself, select more efficient data structures (such as hash tables instead of linear search) to store and access directory information
