What is needed next?

There is an array of resource-intensive tasks.
There are two tools - the master (one who issues challenges) and service by these problems.
About any task knows SERVIS-master (it stores the task queue in its memory) and asynchronously generates tasks to perform demanding tasks and gets answers.
This system works.
The question is - why turn to make a separate service?
3 answers
April 4th 20 at 13:01
To manage, to control resources, to not make a fuss out of their bikes, to Reduce Attack Surface (even if corny) error for different zoom ... a million reasons
Damn, well like the right word, but somehow not felt the need.
Can some directly case? - katelin.Stracke commented on April 4th 20 at 13:04
@Jamila.Stracke, some will not help in understanding. It is necessary or to study architecture or on their skin face the problem - miller_Mitchell70 commented on April 4th 20 at 13:07
April 4th 20 at 13:03
There are many options why it is useful.
1. The queue does not depend on the performance (failure or restart - does not affect the queue itself).
2. The scaling of the star.
3. Change of priorities of processing objects in the queue, any service connected to managing this queue.
4. Flow control: who, how, where, etc.
5. Statistics processing.
April 4th 20 at 13:05
Everything is simple, when you restart the wizard, the RUB, the service queue you can turn on megacasino server, it can be scaled and convenient to raspredelyat tasks if services performers will be a lot.

Find more questions by tags Message queuesRabbitMQDesigning softwareService-oriented architecture