qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Qpid Wiki] Update of "ClusteringAndFederation" by rhs
Date Mon, 25 Sep 2006 20:55:56 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Qpid Wiki" for change notification.

The following page has been changed by rhs:
http://wiki.apache.org/qpid/ClusteringAndFederation

------------------------------------------------------------------------------
+ The following notation is used in all diagrams:
+  * M: message
+  * E: exchange
+  * Q: queue
+ 
+ == Multicast ==
+ 
  {{{
- The following notation is used in all diagrams:
-  M: message
-  E: exchange
-  Q: queue
- 
- 
-                     Multicast
- 
                       M1...Mn
                     +--------> Q
                     |
@@ -17, +16 @@

                     |
                     | M1...Mn
                     +--------> Q
+ }}}
  
  Queue contents are duplicated across all queues. For this scenario PGM
  would be ideal between E and Q, or even directly between E and
  consumers.
  
+ == Load Balancing ==
  
+ {{{
-                   Load Balancing
- 
                       M1
                     +--------> Q
                     |
@@ -33, +33 @@

                     |
                     | Mn
                     +--------> Q
+ }}}
  
  No ordering is guaranteed accross different queues. A naive
  implementation could just be an exchange doing round-robin routing or
  any algorithm of choice. A more complicated exchange could have flow
  control between each queue and the exchange.
  
-                 Multiple Exchanges
+ == Multiple Exchanges ==
  
+ {{{
   M? ---> E1-----+              +-----> Q1
                  |              |
                  | (n*m arrows) |
@@ -48, +50 @@

                  |              |
                  |              |
   M? ---> En-----+              +-----> Qm
+ }}}
  
  Both the Load Balancing and Multicast scenarios can be extended by
  adding multiple exchange nodes wired into the same (or an overlapping)
@@ -89, +92 @@

  have a passive counterpart that supports two methodologies for
  failover. Broker swapout based on virtual IP, or client reconnect to a
  backup IP.
- }}}
  

Mime
View raw message