This topic outlines what you should consider when planning a bus
that consists of multiple servers but no cluster bus members. Having more
than one server provides the advantages of scalability, the ability to handle
more client connections and greater message throughput.
Why and when to perform this task
You can plan a bus that has multiple server bus members, none of
which are members of a cluster.
When planning for a multiple-server bus,
you should consider the following factors:
- The number of messaging engines in the bus and their properties.
- The distribution of destinations in the bus. For performance reasons,
you may decide to place destinations close to associated producers.
- For point-to-point messaging, which bus member should be assigned to holding
messages for a particular queue.
You should also review the planning issues that are common to all topologies.