Chapter 12. Creating Collectives

A collective is a set of ActiveMQ topics and 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:

  • Collectives can be used to limit traffic in large clusters or between sites.

  • Collectives can be used to group nodes together for restricting client access.

Deciding When to Create More

There are a few reasons why you may want to implement multiple collectives in your network:

  • You have more than a thousand servers.

  • You have multiple locations with high latency between them.

  • You have multiple locations and you’d like to reduce the network traffic between them.

  • You want to allow local admins control of their own hosts, while allowing a global team to administer all hosts.

Here are a few reasons you wouldn’t want to implement multiple collectives:

You want fault tolerance in your middleware setup.

Collectives do not intrinsically provide fault tolerance. Fault tolerance can be created by using a network of brokers or master/slave setup, which is 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.

Although you can restrict clients to specific collectives to limit server ...

Get Learning MCollective now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.