## Broker Deployment Options

### Broker functions

The message broker is responsible for routing messages to the correct topic or queue. It is also responsible for providing quality of service features, such as reliability, persistence, security, and high availability.

You can deploy FUSE Message Broker in either standalone or embedded mode. You can also deploy a network of brokers.

### Embedded broker

An embedded broker executes within the same JVM process as the clients that are using its services. So rather than communicating across the network, clients can communicate with the broker more efficiently using direct method invocation.

In addition, if the network fails, clients can continue to send messages to the broker, which will hold the messages until the network is restarted. See Starting an embedded broker

### Standalone broker

A standalone broker does not share its JVM process with clients and instead communicates with clients using a network-based transport connector. See Starting a standalone broker for details.

### Network of brokers

Often a number of brokers can be linked together in a network or cluster of brokers. A network of brokers can use various network topologies, such as hub-and-spoke, daisy chain, or mesh.

Figure 2.3. A Network of Brokers

[D]