We use redis to count the number of visits to articles, and generate yesterday’s click rankings, this month’s click rankings and other data.
The performance is very good, but the disadvantage is that the internal speed of the machine is not enough. Our solution is to write to two machines at the same time, and clear the data of one of them every once in a while.
The current development of redis is greatly influenced by the author. His milestones were not particularly well planned, resulting in great differences and lack of consistency between each version.
After using it, I find queue very useful. And then it would be really nice to do some counters.
Where I think redis should be improved:
Distributed support actually only needs to be supported on the customer service side like memcached.
Are these features of VM useful?
The php driver of redis feels good when using phpredis.
Recently using redis in projects
1.List as message queue
2.Sorted Sets do some intersection/union operations (intersect the friend lists of two users to get common friends, etc.)
We use redis extensively in applications with high performance requirements, and mainly use redis's sorted set, hastset, pub/sub data structures.
Basically, it replaces relational data as a storage service for data persistence in the front-end (applications facing end users). Of course, there are other data storage products behind redis as final data backup.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
We use sorted set to make the ranking system, which is much simpler than the traditional implementation method
We use redis to count the number of visits to articles, and generate yesterday’s click rankings, this month’s click rankings and other data.
The performance is very good, but the disadvantage is that the internal speed of the machine is not enough. Our solution is to write to two machines at the same time, and clear the data of one of them every once in a while.
The current development of redis is greatly influenced by the author. His milestones were not particularly well planned, resulting in great differences and lack of consistency between each version.
After using it, I find queue very useful. And then it would be really nice to do some counters.
Where I think redis should be improved:
Distributed support actually only needs to be supported on the customer service side like memcached.
Are these features of VM useful?
The php driver of redis feels good when using phpredis.
Recently using redis in projects
1.List as message queue
2.Sorted Sets do some intersection/union operations (intersect the friend lists of two users to get common friends, etc.)
We use redis extensively in applications with high performance requirements, and mainly use redis's sorted set, hastset, pub/sub data structures.
Basically, it replaces relational data as a storage service for data persistence in the front-end (applications facing end users). Of course, there are other data storage products behind redis as final data backup.
Let’s talk about some features of Redis that I use: bitset, hashset, sorted set, pub/sub, k-v cache
Can you please talk about this error? Want to know more about it.