[CONF] Apache Qpid > New Page

[confluence]

New Page Page edited by Martin Ritchie Purpose This page is intended to outline the known use cases for running multiple Java Brokers, addressing logged issues and limitations of the current implementation (as of V0.5). It is not about clustering proper. Use Cases High Volume Transient Broker Description The key characteristics of this application scenario are: Broker availability is key Traffic is pub-sub Message Order is not important Currently, for applications with a high residual message load i.e. where message data on the broker remains in memory for some time or consumption lags production such that a backlog is constantly present in the broker queues. This paradigm is reasonably common, partly because publication threads are generally handling only the simple publish call where we often see consumption threads handling writes to RDBMS or other time expensive processing. Thus a rate gap opens up, and creates a data tailback. Result Possible Solution Low Volume Persistent Broker Description Result Possible Solution Change Notification Preferences View Online | View Change | Add Comment --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:commits-subscr...@qpid.apache.org