Shulou(Shulou.com)06/01 Report--

What are the usage scenarios of redis? Many novices are not very clear about this. In order to help you solve this problem, the following editor will explain it in detail. People with this need can come and learn. I hope you can gain something.

It is mainly introduced from the following aspects:

Distributed lock

Interface current limiter

Order caching

Redis and DB data consistency processing

Prevent cache penetration and avalanches

Distributed session sharing

Order caching

The storage structure of the entire order is as follows:

Use Redis's zset data structure to store each user's order, arranged in reverse order, the user's unique identity as key, the user's order set as value, and the timestamp of the order creation time + the last three digits of the order number as scores.

Why not directly use the timestamp of the time the order was placed as a score? Because the time to place an order is only accurate to seconds, multiple orders may occur in the same second, so the same score will appear, which can basically be avoided by adding three digits after the order number.

Just put the user's first N orders, because very few users will view the orders from a long time ago, which will save a lot of space. If there are users who need to view the orders after the first N, and then query from the database, of course, this probability is relatively small.

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.