FairCom MQ Broker connections
Actions to manage FairCom MQ broker connections
The JSON Hub API: broker connection actions are part of the JSON MQ API. This section provides actions to configure, delete, describe, and list broker connections.
There are several useful reasons to create connections between MQTT brokers.
The clients of one broker can publish and subscribe to topics locally and you can configure FairCom MQ to deliver and receive messages on behalf of that client to brokers in many locations.
You can easily create, manage, and reconfigure a global communication network of MQTT brokers and local clients do not know they are communicating globally with the same message guarantees they expect for local communications. For example, a client connected to a local instance of FairCom MQ can be blissfully unaware that it is reliably communicating with brokers in the cloud, other data centers, factories, offices, buildings, hospitals, cities, and so forth.
You can easily and quickly publish messages to many millions of subscribers by chaining together brokers. For example, one broker can publish to 100 brokers and each of them can publish to another 100 brokers, and so forth. Each of these brokers can easily deliver messages to thousands of subscribers.
FairCom MQ and FairCom Edge are well suited to create reliable connections to external brokers because they persist every message and guarantee in-order message delivery even when external brokers are offline for extended periods.
Action | Description |
|---|---|
| |
| |
| |
|