You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -469,12 +469,12 @@ Is very similar to the previous example, we just have an extra `addRequest` call
469
469
### Multiple Consumers ###
470
470
471
471
It's a good practice to have a lot of queues for logic separation. With a simple consumer you will have to create one worker (consumer) per queue and it can be hard to manage when dealing
472
-
with many evolutions (forget to add a line in your supervisord configuration?). This is also useful for small queues as you may not want to have as many workers as queues, and want to regroup
472
+
with many evolutions (forget to add a line in your supervisord configuration?). This is also useful for small queues as you may not want to have as many workers as queues, and want to regroup
473
473
some tasks together without losing flexibility and separation principle.
474
474
475
475
Multiple consumers allow you to handle this use case by listening to multiple queues on the same consumer.
476
476
477
-
Here is how you can set a consumer with multiple queues:
477
+
Here is how you can set a consumer with multiple queues:
0 commit comments