.NET message queue processing between master and production servers

I am trying to find a better way to create a master worker architecture for easy delegation delegation.

1 master process that delegates tasks to multiple workflows. - The master must constantly run and delegate jobs to workers (and perform other tasks). Workers (on different servers) just have to get the job, process it and report. - the master process will receive a queue of tasks and transfer them to work nodes, which will then process the request and notify the wizard that the task has been processed. The wizard does not have to wait for the completion of the work, but can simply delegate the task, and then receive an update from the employee when it is completed.

What would be the best way to facilitate this communication in .NET? I already have class libraries that do work processing, but I'm looking for a good method of communication.

Msmq? Windows service? Remoting?

thank

+3
source share
2 answers

For this purpose, I used WCF with net.tcp bindings, with a callback interface, so that Master Control knew that the job was done (yes, it was called "MCP", the processes that initiated the tasks were called "Sark", and the network was named "Game Grid", go to the picture).

"Sark" , Windows ( " " ), MCP . , , , - Windows Service, , - , , MCP . MCP " " GUI.

.Net DLL- . "Sark" , AppDomain, AppDomain, , . MCP Sarks.

, Sark MSMQ ( 10 ), . MCP , , . : , 80%, 80 "" , , , , 10% . , .

net.tcp WCF , " " . : - , (, , FoxPro, ODBC FoxPro Microsoft 64- - , 32- 64- ), - , , IP-, , . MCP .

MSMQ, , , MCP , , - , MCP " t .

+3

MSMQ - , , - - "fire and forget". , , . WCF MSMQ - MSMQ - . , Windows , AppFabric, - IIS. , Windows Server 2008 R2, Windows, .

+3

Source: https://habr.com/ru/post/1794251/


All Articles