You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: Users.

You can view and copy the source of this page.

Return to BrandMeister Server Clustering.

BrandMeister Server supports several ways to make server clusters in a datacenter. In fact each cluster node is separate brandmeister process and can runs as a normal node but the main topic is how to reach zero-latency if we have more than one node close each to the next one.

We may have several reasons to think about clustering:

Running several processes on the same host[edit]

BrandMeister Server supports this option. This can solve a problem of reached performance of single CPU core. Each server process may utilize separate core. At the same time Tarantool and Mosquitto can be shared. You can balance load of different protocol stacks by this way, for example move "HyteraPTT RoIP" to separate process.

Reaching zero-latency[edit]

Regular transport for cummunications between nodes of BrandMeister Server is FastForward on top of UDP. This makes a traffic globally routed, but... it has no guaranies of delivery, packets can be reordered, we have to use jitter buffer.

How to have reliable delivery with zero latency if we can be sure of environment availability for this?

FastForward supports several options for that:

All these options cn be used at the same time by defining records at the space OverriddenNodes at local Registry.


For all types of communications except shared memory FastForward uses unique numeric port number. It uses as:


Under Tarantool Registry: