Consider the following high level design:
I have a server (call it rabbitMQ) and it create some tasks and place them in a messaging queue.
some servers (A,B,C,D...) 'see' that there are some tasks on the queue and they take a task to process on their end.
My questions:
- is this explanation is correct in terms of distributed system design? and
- if so where does the celery comes into play? is it on the serverA/B or C side? so each has its own celery?
