Using Replication with DMR
You can take advantage of disaster recovery (using replication and Config-Sync) while using Dynamic Message Routing (DMR) to dynamically route messages through your event mesh. DMR provides a means to interconnect instances of Solace PubSub+ event brokers so that messages published by clients hosted by one broker can be consumed by clients hosted on another.
For example, imagine a three-region replication-enabled event mesh, interconnected using DMR:
- Each region (depicted by a gray oval) is a separate DMR cluster.
- In each region there are two nodes, each of which consists of one High-Availability (HA) pair.
- Each node in the network is connected to every other node by a DMR link:
- Nodes between clusters (regions, in this example) are connected by external DMR links
- Nodes within the same cluster (for example, Seattle and San Jose) are connected by internal DMR links.
This example topology is illustrated in the following diagram:
In this example,
- in the USA West region, the Seattle and San Jose nodes form a replication group, with VPNs Red and Blue active in Seattle, and VPN Green active in San Jose.
- in USA East, the New York and Chicago nodes form another replication group, with VPNs Red and Blue active in New York, and VPN Green active in Chicago.
- in Canada East, a replication group has been established between the Toronto and Montreal nodes, with VPNs Green and Blue active in Toronto, and VPN Red active in Montreal.
Within this fully connected mesh, the brokers are able to determine how messages should be routed. Each node advertises the list of its connected DMR neighbors and replication mates, allowing all nodes to build an accurate internal model of the network. As nodes are added or removed, this same mechanism allows the other nodes to dynamically adjust their internal representation of the DMR network.
Because the nodes in the network are aware of the replication mates, messages are routed as if the replication group were a single node:
- DMR data channels are active only on the active message VPNs, as shown below.
- Messages are not propagated over DMR links between replication mates. Instead messages are replicated over the replication bridge as normal.
- Nodes that are connected to replication mates use a single shared data channel and queue for both members of the replication group (for more information, see Configuring Cluster Links with Replication).
Replication mates must be in the same cluster, connected with an internal DMR link.
In versions 10.0.1 and later, replication may be enabled or disabled on all DMR-enabled Message VPNs. If replication is disabled on a DMR-enabled Message VPN, messages are propagated over the DMR link between replication mates instead of the replication bridge. Using the previous example, if replication is disabled on Message VPN Blue for nodes in the Canada East cluster, the resulting topology looks like this:
In this example, no DMR bridge is configured from the Toronto node to New York node for Message VPN Blue.
To learn how to configure replication with an event mesh, see Configuring Replication with a DMR Network.