More actions
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
We have investigated 3 communication techniques so far: remoting, WCF and MSMQ. You can find the whole story here [[Remoting,WCF and MSMQ for CatTask|Remoting,WCF and MSMQ for CatTask]] . At the moment, we are designing the module using MSMQ with the help of Rhino Service Bus. | We have investigated 3 communication techniques so far: remoting, WCF and MSMQ. You can find the whole story here [[Remoting,WCF and MSMQ for CatTask|Remoting,WCF and MSMQ for CatTask]] . At the moment, we are designing the module using MSMQ with the help of Rhino Service Bus. | ||
== Rhino Service Bus == | == Rhino Service Bus == | ||
Rhino Service Bus is an [ESB|http://en.wikipedia.org/wiki/Enterprise_service_bus en.wikipedia.org/wiki/Enterprise_service_bus] | |||
== Buses design for CatTask == | == Buses design for CatTask == | ||
Revision as of 11:28, 19 March 2009
Communication in Cattask v2009
What kind of communication do we need?
In the real production environment, because of the use of network balancing, one CatGlobe site is deployed in three separate servers. Besides, we decided that there will be one "Cattask" for one deployed instance of a site. The running production environment should look like:
The problem is that the three cattasks won't run independently. Instead, they must contact with each others to share information about scheduled tasks, tasks execution...
So what communication technology should we use?
We have investigated 3 communication techniques so far: remoting, WCF and MSMQ. You can find the whole story here Remoting,WCF and MSMQ for CatTask . At the moment, we are designing the module using MSMQ with the help of Rhino Service Bus.
Rhino Service Bus
Rhino Service Bus is an [ESB|http://en.wikipedia.org/wiki/Enterprise_service_bus en.wikipedia.org/wiki/Enterprise_service_bus]