Redis is used as a message queue: for example, send an email. Do you think it’s better to send them one by one? Or send them all at once? Queue queue, just come one by one. Of course, most of the time, the first type is better. The so-called 抗大并发 means that the system can still work in an orderly manner under high load. You ask if it’s suitable, I think it’s suitable if you feel comfortable using it.
Redis can be used as a message queue, and its performance is not bad, but it may be a bit unreliable in terms of resistance to large concurrency because it does not support clusters. There is really no connection between the query function and the queue.
That’s it. The function we need to do now is similar to a score query, which is mainly displayed on the web page.
1. The user clicks on the score query 2. The button text shows that it is querying, and the asynchronous query using ajax starts. 3. Internal logic calls the interface for query 4. Returns json data to the client. 5. It shows that the query is successful and is jumping. 6. Display the results page.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Based on the content of this question, my answer is:
Suitable, very suitable...
Message queue is mainly used for: writeoperations
under large concurrencyIt is recommended to use elasticsearch
Redis is used as a message queue: for example, send an email.
Do you think it’s better to send them one by one? Or send them all at once? Queue queue, just come one by one.
Of course, most of the time, the first type is better. The so-called
抗大并发means that the system can still work in an orderly manner under high load. You ask if it’s suitable, I think it’s suitable if you feel comfortable using it.Characteristics of queue, asynchronous, non-real-time, distributed
Redis can be used as a message queue, and its performance is not bad, but it may be a bit unreliable in terms of resistance to large concurrency because it does not support clusters.
There is really no connection between the query function and the queue.
Do you want to use redis for caching?
That’s it. The function we need to do now is similar to a score query, which is mainly displayed on the web page.
1. The user clicks on the score query
2. The button text shows that it is querying, and the asynchronous query using ajax starts.
3. Internal logic calls the interface for query
4. Returns json data to the client.
5. It shows that the query is successful and is jumping.
6. Display the results page.