Difference between revisions of "Cattaskv2009 Communication"
| Line 27: | Line 27: | ||
[[Image:CatTask A simple bus.JPG]] | [[Image:CatTask A simple bus.JPG]] | ||
| − | *In the <bus> element we can see an end point. It is the | + | *In the <bus> element we can see an end point. It is the queue which the bus monitors for incoming messages. When messages come, the bus will receive the messages from the queue and invoke the appropriate consumers to process them. For example: in the image below, we have a consumer called CatGlobeMessageController which implements the IConsumerOf<HelloCatGlobe> interface. When messages of the type come, the bus will invoke CatGlobeMessageController to process them. |
[[Image:CatTask A simple consumer.JPG]] | [[Image:CatTask A simple consumer.JPG]] | ||
| Line 35: | Line 35: | ||
- Send with an explicitly specified end point (queue). | - Send with an explicitly specified end point (queue). | ||
| − | - Send without a specified endpoint. We need to specify the queues (message owners) of | + | - Send without a specified endpoint. We need to specify the queues (message owners) of the message type. Notice the <messages> section in the configuration block above: it says that all the messages of types which are defined in the CatGlobe.Messages.WebShop namespace will be sent to the "msmq://web/WebShop" end point. So is the second setting for CatTask. |
| − | |||
| − | |||
== Buses design for CatTask == | == Buses design for CatTask == | ||
Revision as of 03:37, 23 March 2009
Contents
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 (RSB) is an ESB which is built on the top of MSMQ. Since the bus behaviours are mainly specified by its configuration file, we'd better look at the configuration to learn how the bus works:
<facility id="rhino.esb" >
<bus threadCount="1" numberOfRetries="5" endpoint="msmq://localhost/ownqueue" />
<messages>
<add name="CatGlobe.Messages.WebShop" endpoint="msmq://web/WebShop"/>
<add name="CatGlobe.Messages.CatTask" endpoint="msmq://catmaxb/CatTask"/>
</messages>
</facility>
In short, a Rhino service bus:
- In the <bus> element we can see an end point. It is the queue which the bus monitors for incoming messages. When messages come, the bus will receive the messages from the queue and invoke the appropriate consumers to process them. For example: in the image below, we have a consumer called CatGlobeMessageController which implements the IConsumerOf<HelloCatGlobe> interface. When messages of the type come, the bus will invoke CatGlobeMessageController to process them.
- Can send messages to other queues (of course!!!). The point here is that it has two Send APIs:
- Send with an explicitly specified end point (queue).
- Send without a specified endpoint. We need to specify the queues (message owners) of the message type. Notice the <messages> section in the configuration block above: it says that all the messages of types which are defined in the CatGlobe.Messages.WebShop namespace will be sent to the "msmq://web/WebShop" end point. So is the second setting for CatTask.
