The problem is that when we push tasks to the queue, the tasks that we inevitably push are various, such as emails and text messages. when the background work process obtains tasks, the idea is often banned, and I think that the task is pushed by category, so do I need to retrieve the task by category... the problem is that when we push tasks to the queue, the tasks that we inevitably push are various, such as emails and text messages. when the background work process obtains tasks, the idea is often banned, and the idea is that I push tasks by category, so whether to obtain them by category is also necessary, then there may be multiple task processing processes at this time, the only difference is the parameter of the task category. Isn't the design good?
Reply content:
The problem is that when we push tasks to the queue, the tasks that we inevitably push are various, such as emails and text messages. when the background work process obtains tasks, the idea is often banned, and the idea is that I push tasks by category, so whether to obtain them by category is also necessary, then there may be multiple task processing processes at this time, the only difference is the parameter of the task category. Isn't the design good?
Determine based on the business scenario. if the business volume is large, it is obviously inappropriate to use a process to process the task.
We recommend that you use different queues to process different information. although parameters can be used separately, they are not conducive to the isolation and expansion of large concurrency, for example, if a service only pays attention to the text message, you can listen to the text message queue.