IBM MQ has introduced a new phrase to its catalog, the  Uniform Cluster . In IBM MQ 9.1.2,  queue managers can be aware that they’re being us ed for this exact purpose. And this solves  some of the challenges that users would have had to address: How do I ensure that my multiple application instances are evenly distributed across those  queue managers? Also, how do I ensure that every queue manager has at least one  consuming application for each queue?  If these questions are left to chance with a CCDT to load balance, there are no guarantee of  success (Figure 9-21 on page 590). If a queue manager is stopped for maintenance, applications can reconnect to a remaining  queue manager (for example with auto reconnect). But how do applications connect back to  that stopped queue manager after it is restarted? See Figure 9-22. If a configuration change brings in a new queue manager, perhaps to scale up, how does it  get a fair proportion of connected applications? See Figure 9-23. Figure 9-21 Unbalanced connections with traditional CCDT configuration Figure 9-22 Maintenance of queue managers Figure 9-23 Scaling out with additional queue managers To date, the preceding issues have typically been solved either through increased application  logic, or through manual operations being performed. With the release of IBM MQ 9.1.2 on  590  Accelerating Modernization with Agile Integration