Hello, I have been toying with the idea of moving into a Bus based model for
component communication for our distributed application.  Such that
producer-clients can send messages to a meta-destination, and the closest
consumer-client can pick the message up, then have the response return to
the originating client.

Basically we have different classes of messages, of which each could have a
particular type.  Consumers and producers of these messages don't really
need to know where the other end-point exists.  They only need to create a
message, put it on the bus and optionally wait for a response to that
message.

In a simple example, lets say that there are 4 virtual machines nodes
each on a seperate pyhsical machine.  Below is a diagram of the pyhsical
distance (or network distance):

      +--------+---------+-------+  bus
      |        |         |       |
     [p1]     [c1]      [c2]    [p2]
               |         |
               DB        DB

 [px] are message producers (clients that are making requests)
 [cx] are consumers that can process client requests

If [p1] puts a message on the bus for lets say authentication, the closest
consumer is [c1].  [c1] reads the message looks up the information in the
database, then sends a resposne back to [p1].  The same would be true for
[p2] and [c2].  If for some reason [c1] went down, then messages from [p1]
would be picked up by [c2].

I am wondering if you have an suggestions or comments on building such a
Bus infrastructure on top of SwiftMQ?


--jason



------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to 
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/




Reply via email to