What’s New in HiveMQ 4.13?
The HiveMQ team is proud to announce the release of HiveMQ Enterprise MQTT Platform 4.13. This release significantly enhances integration with Amazon Web Services through the HiveMQ Enterprise Extension for Amazon Kinesis Data Streams and includes several performance and security enhancements for the HiveMQ platform.
Highlight
Added bidirectional message support to the HiveMQ Enterprise Extension for Amazon Kinesis with the ability to consume Amazon Kinesis messages and send them to your IoT devices.
Increased IoT data ingestion options with Amazon Kinesis Extension
The HiveMQ Enterprise Extension for Amazon Kinesis provides cloud-native integration with Amazon Kinesis Data Streams. Together with the HiveMQ Enterprise Extensions for Kafka and Google Pub/Sub, our Kinesis extension gives you greater freedom to select the cloud service providers that fit your needs. The HiveMQ Enterprise Extension for Amazon Kinesis lets you move MQTT data bidirectionally between your HiveMQ broker and Amazon Kinesis Data Streams at hyper-scale.
How it works
Amazon Kinesis is a suite of fully-managed Amazon Web Services (AWS) designed to ingest, process, and analyze data streams. Amazon Kinesis Data Streams can capture data from various sources as part of the Kinesis suite.
This release of our Amazon Kinesis extension supports bidirectional message flow between MQTT clients and Amazon Kinesis Data Streams via the HiveMQ broker. The extension can be configured flexibly to forward messages to one or more Kinesis data streams or consume messages from one or more Kinesis data streams.
How it helps
The MQTT data you move to Amazon Kinesis Data Streams is immediately available for further processing with other AWS services. For example, this makes it possible to use the Kinesis Data Analytics service to stream your MQTT device data to any AWS data storage service.
The newly added Kinesis to MQTT routing allows the HiveMQ extension to consume messages that your AWS backend services process and store on AWS Kinesis Data Streams. From there, your fully-featured HiveMQ MQTT broker handles message delivery to your connected IoT devices.
Other Noteworthy Fixes and Improvements
HiveMQ Enterprise MQTT Broker
- Added user feedback during HiveMQ startup to provide detailed information when native SSL is enabled for a deployment.
- Streamlined the client connection context to reduce memory usage per client connection.
- Improved unsubscribe handling to reduce memory consumption per connected client.
- Fixed an issue that generated an exception when a node briefly disconnected from the cluster.
- Fixed an issue that could prevent a reconnecting client from receiving further messages in rare situations.
- Fixed an issue that could cause the license expiry metric to display an incorrect value after a license update.
HiveMQ Enterprise Security Extension
- Mitigated an issue in the HiveMQ Enterprise Security Extension that could negatively impact database operations when the connection to an SQL database is impaired.
- Improved handling in the HiveMQ Enterprise Security Extension to ensure that changes to authorization data in the file-realm configuration file are recognized as expected on Kubernetes.
- Improved user feedback in the HiveMQ Enterprise Security Extension when an MQTT client permission cannot be built.
HiveMQ Enterprise Bridge Extension
- Fixed an issue in the HiveMQ Enterprise Bridge Extension that could cause connection errors for MQTT clients that use TLSv1.2 if native SSL is enabled for the HiveMQ broker.
Get Started Today
To upgrade to HiveMQ 4.13 from a previous HiveMQ version, take a look at our HiveMQ Upgrade Guide. To learn more about all of the features we offer, explore the HiveMQ User Guide.
About HiveMQ Team
We love writing about MQTT, IoT protocols and architecture in general. Our experts are here to help, so reach out to us if we can help!
Contact HiveMQ
