The HiveMQ Enterprise Bridge Extension enables HiveMQ to bridge to one or more MQTT brokers for scalable, reliable, and bi-directional exchange of MQTT messages.
Category: Data Integration
Version: Bundles with HiveMQ
The HiveMQ Enterprise Bridge Extension enables HiveMQ to bridge to one or more MQTT brokers for scalable, reliable, and bi-directional exchange of MQTT messages. The Enterprise Bridge Extension makes it possible to:
Enable customizable, bi-directional topic mapping.
Configure a set of topic filters that forward matching messages to specific destination topics at another MQTT broker.
Achieve finely-grained configuration of the source topic filter and destination topic with the use of all MQTT-specific variables as well as configuration-specific templating.
Enable extensive logging capabilities and useful metrics for monitoring.
The HiveMQ Enterprise Bridge Extension enables HiveMQ to bridge to one or more MQTT brokers. For example, you can set up regional MQTT broker clusters that stream MQTT data to a central MQTT broker in a data center that is used for regional data analysis.
The Bridge Extension allows local HiveMQ brokers at individual sites to bridge the data to the HiveMQ broker on the enterprise.
Determine what data needs to be sent for centralized communication and data exchange at the enterprise level and what is stored only locally.
Create a federation or topology of multiple broker clusters to optimize network performance and increase efficiency.
Use extensive logging and metrics to monitor application performance and quickly troubleshoot issues.
HiveMQ extensions are plugins that provide seamless integration with streaming services, databases, data warehouses, and security services. There is a Custom SDK to build tailored extensions for specific integration needs.
Extensions usage scales along with the rest of the cluster and each enterprise extension is designed and tested for use in a cluster.
Extensions run on each cluster node, so if a node exits the cluster the extension will be present on the replacement node.
No separate nodes to manage. Easily manage cluster-wide configuration in a Kubernetes cluster with the HiveMQ Operator.