For example, add a series of activities, have a start time, and then arrive at the start time automatically set to start state, end set to end state.
Also, query the database or put it on Redis?
Reply content:
For example, add a series of activities, have a start time, and then arrive at the start time automatically set to start state, end set to end state.
Also, query the database or put it on Redis?
Strictly speaking, the queue is just to send messages, not to do the task-based (although through delayqueue can also be achieved), but it is best to pass the crontab
Start the activity, the end time can be directly in the code to judge, preferably have a background control of the start of this series of activities, if your business scenario is different, according to what you said, the proposed use of crontab, simple direct
While querying the data, personal advice is to store the database, query Redis, update at the same time
Query database slow, concurrency low
If at the same time on-line activities, there is a certain number of concurrent, it should be good cache preparation, to prevent the database hanging.