RabbitMQ deployment option: standalone machine - Genetec Mission Control™

Genetec Mission Control™ Deployment Guide

Applies to
Genetec Mission Control™
Last updated
Content type
Guides > Deployment guides
English (United States)
Genetec Mission Control™

You can deploy RabbitMQ on a standalone machine separate from all other components of the Genetec Mission Control™ installation.

Benefits: RabbitMQ on a standalone machine

RabbitMQ resources are not shared
Other services do not use the same resources and therefore do not impact RabbitMQ performance or availability.
Low maintenance
Only two machines to monitor and manage; one for RabbitMQ and one for all other Genetec Mission Control™ components.

Drawbacks: RabbitMQ on a standalone machine

Complex deployment
You must manually execute the Genetec Mission Control installer on the second machine, clear all component installation options and select only the RabbitMQ option.
Higher latency in communication between components
There might be a slight delay in communications between RabbitMQ and the other services.
Greater impact from environment issues
Network environment issues between RabbitMQ and other services would directly impact service up-time.
No fault resilience or fault tolerance
If the machine with RabbitMQ goes offline you would lose the Incident Manager role as well along with all the data on incident triggers.

If the machine with the other components goes offline you would lose availability of all services as the Security Center Directory would be offline as well.

Updating your Windows machine might incur downtime
Every time you update your system, there is downtime incurred while the system reboots.

Quality of service

Using this deployment architecture implies that service quality relies more on your system infrastructure. The quality of service would be directly dependent on the quality and reliability of your network infrastructures.