This example deploys a self-hosted version of HiveMQ.
HiveMQ is a high-performance, enterprise-grade MQTT (Message Queuing Telemetry Transport) broker that enables seamless communication between devices and applications using the MQTT protocol. MQTT is widely used for real-time data exchange and communication in IoT (Internet of Things) applications, where low bandwidth and reliable messaging are crucial. HiveMQ provides various features and options for deploying it in high availability and clustered configurations.
This container is based on community edition docker image and doesn't have control center feature. If you want Enterprise Edition then update the config.xml file with necessary license information and update the Dockerfile with the Enterprise Edition base image. But project is configured to work for any docker image of hiveMQ.
- MQTT 5.0 Support: HiveMQ supports the MQTT 5.0 specification, providing advanced features such as shared subscriptions, enhanced security, message properties, and more.
- High Performance: HiveMQ is designed for high performance and low latency, making it suitable for applications that require real-time communication.
- Scalability: HiveMQ can be easily scaled horizontally to handle a large number of concurrent connections and messages.
- Reliability: It ensures message delivery even in unreliable network conditions. Persistent sessions and durable message storage mechanisms prevent message loss.
- Security: HiveMQ offers comprehensive security features, including TLS/SSL encryption, client authentication, access control, and integration with external authentication mechanisms.
- Websockets: HiveMQ supports MQTT over WebSockets, allowing devices and applications to communicate over HTTP/HTTPS ports.
- Advanced Clustering: HiveMQ supports clustering, enabling you to set up multiple instances that work together to provide high availability and fault tolerance.
- Session Management: It provides flexible session management options, including session expiration, resumption, and storage.
- Retained Messages: HiveMQ allows the broker to store the last known state of a topic, ensuring that new subscribers immediately receive the latest data.
- QoS (Quality of Service): HiveMQ supports MQTT's QoS levels, ensuring that messages are delivered as required by the application's quality-of-service requirements.
- HiveMQ
- Click the Railway button ๐
- Add the required environment variables
- Deploy
- Access HiveMQ Control Center from Railway URL
- Use can login using default credentials
admin
andhivemq
- You should see the dashboard with all analytics and metrics of your HiveMQ instance with connected clients and messages infomration in real-time
- You can also use the MQTT Websocket client to publish and subscribe to topics
- By default, the MQTT Websocket client is available at
https://<your-railway-url>/mqtt
- With help of reference python code
example.py
you can test your HiveMQ instance - You can also view real-time client infomration from the HiveMQ Control Center
- Also you can disconnect clients from the HiveMQ Control Center
- HiveMQ also provides options for subcriptions and topics
- Using trace functionality you can view all the messages that are published and subscribed
- Finally, you can backup and restore your HiveMQ instance from the HiveMQ Control Center
- Instance is configured with cluster with static discovery. you can add multiple instances to the cluster by modifying the config file
config.xml
and adding the instances to thestatic-discovery
section. Follow the official docs for more information. - Enjoy ๐