Collective is a set of ActiveMQ
queues used to group request traffic. In small installations you should use a single
Collective. The installation we have done in this book uses the default collective name
mcollective for all configurations.
You may want to create multiple collectives for the following reasons:
There are a few reasons why you may want to implement multiple collectives in your network:
Following are a few reasons you don’t want to implement multiple collectives:
You want fault tolerance in your middleware setup.
Sub-Collectives do not intrinsically provide fault tolerance. That can be created by using a Network of Brokers or Master/Slave setup, as documented in ActiveMQ Clusters. Collectives are most effective at limiting traffic when placed on brokers localized to each site.
You want to implement barriers for authorization control.
While you can restrict clients to specific collectives to limit server access, this isn’t a granular authorization ...