Use this task to help you plan for the issues that are common to all topologies.
You need to consider the sizes of messages. Larger messages will increase the space a data store requires.
You can select different data store topologies depending on your requirements; for more information see Planning the configuration of a messaging engine to use a data store.
For point-to-point messaging you define bus destinations as queues, and for publish/subscribe messaging you define bus destinations as topic spaces. For point-to-point messaging, only you must select one bus member, as the assigned bus member that is to hold messages for the queue. This action automatically defines a queue point for each messaging engine in the assigned member.
You can also define alias destinations to provide a level of abstraction between applications and the underlying target bus destinations. Applications interact with the alias destination, so the target bus destination can be changed without changing the application
The reliability quality of service for messages on a destination has implications for performance and the amount of space required for a data store. Higher levels of reliability impact on performance and increase the space a data store requires because fewer messages are discarded.
You should decide how you want to use the bus destinations because you can configure a bus destination to prevent producers sending messages to the destination, or consumers receiving messages from the destination.