10.2. Broker Federation Use Cases

Broker Federation is useful in a wide variety of scenarios. Some of these have to do with functional organization; for instance, brokers can be organized by geography, service type, or priority. Here are some use cases for federation:
  • Geography: Customer requests can be routed to a processing location close to the customer.
  • Service Type: High value customers can be routed to more responsive servers.
  • Load balancing: Routing among brokers can be changed dynamically to account for changes in actual or anticipated load.
  • High Availability: Routing can be changed to a new broker if an existing broker becomes unavailable.
  • WAN Connectivity: Federated routes can connect disparate locations across a wide area network, while clients connect to brokers on their own local area network. Each broker can provide persistent queues that can hold messages even if there are gaps in WAN connectivity.
  • Functional Organization: The flow of messages among software subsystems can be configured to mirror the logical structure of a distributed application.
  • Replicated Exchanges: High-function exchanges like the XML exchange can be replicated to scale performance.
  • Interdepartmental Workflow: The flow of messages among brokers can be configured to mirror interdepartmental workflow at an organization.