Releases: rmqtt/rmqtt
0.15.0-beta.4
- Remove gRPC client configuration from rmqtt, added gRPC client configuration to rmqtt-plugins/rmqtt-cluster-raft.toml
- Add grpc_server_actives and grpc_clients_actives to stats.rs
- Optimize build version information display
- Improved gRPC handling, add streaming-based message forwarding.
- Forward inter-node messages using gRPC streaming mode.
0.15.0-beta.3
Update Overview
This release introduces a series of systematic optimizations focusing on network stack refactoring, protocol adaptation, deployment flexibility, and feature modularity. Highlights include:
- Refactored the network layer based on the Tokio asynchronous runtime, removing dependency on the
ntexframework; - Added support for multiple protocols including TCP, TLS, WS, and WSS, with a standardized transport protocol adaptation layer;
- Enabled parallel binding of multiple listeners for heterogeneous network endpoints and internal/external network isolation;
- Provides a library mode for seamless integration into user projects, enabling flexible embedding and on-demand customization;
- Introduced 12 optional feature modules with compile-time selective inclusion;
- Established a standardized plugin extension point mechanism for protocol extension and business logic injection.
1. Modular Refactoring of the Network Layer
The network layer has been completely refactored using Tokio, replacing the ntex framework and its MQTT implementation with a self-developed asynchronous network stack to improve performance and decouple framework dependencies.
The ntex-mqtt codec components are retained and optimized to balance protocol maturity and compatibility, enhancing code reusability.
2. Native Multi-Protocol Support
A unified protocol adaptation layer is introduced with full support for TCP, TLS (MQTT over SSL), WebSocket (WS), and its secure variant WSS.
The implementation adheres to standard specifications such as RFC 6455 and RFC 8446, allowing users to flexibly configure access channels according to network environments and security policies.
3. Parallel Listener Binding Mechanism
A single broker instance can launch multiple listeners in parallel, with each listener independently configurable in terms of protocol type, binding address, port, and related parameters.
This allows flexible binding to various network endpoints and protocol channels. Through fine-grained configuration, users can precisely control different networks, protocols, performance, and resource usage to meet high concurrency and multi-scenario deployment requirements.
- Flexible Deployment: Each listener can have custom parameters (e.g., max connections, TLS certificate paths, heartbeat timeouts), supporting diverse deployment scenarios;
- Internal/External Network Isolation: Separate listeners can be used to isolate internal management traffic from external business traffic, enabling clear boundaries and controllable access policies;
- Operations-Friendly: Simplifies integration with load balancers and firewall rules, easing deployment and monitoring configuration.
4. Library Mode Embedding
Released as a crate-level library, rmqtt can be easily embedded into user services by simply adding it as a Cargo dependency. This integration model supports deep customization and feature trimming, making it ideal for microservices and edge computing scenarios.
To use the RMQTT crate (version 0.15.0-beta.2) in your Rust project, refer to: https://crates.io/crates/rmqtt/0.15.0-beta.2
5. Feature Matrix for Optional Trimming (12 Features)
A modular feature system with 12 components is built under Cargo’s [features] configuration, supporting flexible compile-time feature combination:
- Reduces unnecessary dependencies and resource consumption;
- Controls the final binary size and improves runtime efficiency;
- Supports minimal integration and deployment scenarios.
6. Plugin-Based Extension Mechanism
A non-intrusive plugin architecture is adopted, defining standardized extension interfaces (Extension Points) to support:
- Runtime hot-plugging of custom components;
- Extending features like authentication, authorization, and message routing without modifying core code;
- Deep customization needs for protocol extension and business logic.
Note: This update strictly preserves the original functional semantics while optimizing architecture and expression. No undisclosed functional modules have been added. All features are traceable to the original design goals.
0.13.0
0.12.1
0.12.0
0.11.0
- 'rmqtt-http-api'
- '/metrics/prometheus', reset Prometheus GaugeVec on every refresh, fix the issue of statistical data being duplicated and accumulated. #132
- '/health/check', Optimize the health check API and adjust the data output format. #132
- '/brokers/{node}' and /nodes/{node}, Optimize the 'running' field value of HTTP API '/brokers/{node}' and /nodes/{node}. #132
- Adjust the display format of node status in /api/v1/stats/sum and /api/v1/stats to Boolean type. #148
- /v1/brokers and /api/v1/nodes return rustc_version #128
- 'rmqtt-cluster-raft'
- The cluster node health check feature, when enabled, will actively exit the program when a node becomes unavailable. This feature helps
prevent issues such as network partitioning (split-brain), ensuring that connections on the unavailable node can be re-routed through the
cluster load balancer to other available nodes. #133 - Add plugin document 'cluster-raft.md' #134
- The cluster node health check feature, when enabled, will actively exit the program when a node becomes unavailable. This feature helps
- Pin or upgrade some dependency versions. #136
- 'rmqtt-retainer'
- 'rmqtt-bridge-egress-kafka'
- Fix the timestamp issue, it should be in milliseconds. #144
- 'rmqtt-sys-topic'
- Remove message discard events from the $SYS system topics. #145
- Change the message dropped log level to DEBUG. #137
- To monitor message loss, you can use the following HTTP APIs: '/api/v1/metrics', '/api/v1/metrics/prometheus', or listen for the message_dropped event via a webhook.
- Add a timeout to gRPC message delivery. #146
- Periodically check the availability of the gRPC connection using Ping messages. #147
- Optimize message forwarding between nodes by removing the retry-once feature. #147
- Fix the issue where setting the configuration option message_expiry_interval to 0 in rmqtt.toml causes messages to expire immediately. The intended behavior should ensure messages never expire. #141
- Fix the potential overflow issue in multiplication operations. #142
0.10.0
- Add plugin
rmqtt-bridge-ingress-pulsar. #121 - rmqtt-bridge-egress-pulsar
rmqtt-message-storageandrmqtt-session-storagenow supportredis-clustermode. #119- Optimize the connection handshake process. #116
- rmqtt-cluster-raft
- Snapshot compression algorithm enabled, default: zstd
- Add 'client_connack_unavailable_error' metric. http-api#/api/v1/metrics
- Prometheus format metric data supports conditional queries. #114
- Session count limit per node. #109
#Maximum session limit, 0: no limit, default value: 0 mqtt.max_sessions = 0 - Fixed the issue of potentially inaccurate inflight message statistics. #108
- Upgrade and organize dependency libraries. #122
0.9.0
0.8.0
- Add plugin 'rmqtt-auth-jwt' #92
- Optimize the method for retrieving the current time
- ACL permission preset feature
- Add ACL permission preset feature to 'rmqtt-auth-http'
- rmqtt-cluster-raft
- Remove config item 'storage_available'. Affected plugins: rmqtt-bridge-ingress-kafka, rmqtt-bridge-ingress-mqtt, rmqtt-http-api, rmqtt-sys-topic. #91
- Update dependencies, tikv-jemallocator = "0.6", salvo = "0.71", tokio-cron-scheduler = "0.11"
0.7.0
- Add plugin "rmqtt-bridge-egress-pulsar". #82 https://github.com/rmqtt/rmqtt/commit/f382dd942e299cb589bc4545d5aa961ef535fe26
- Add plugin 'rmqtt-auto-subscription'. https://github.com/rmqtt/rmqtt/commit/586c562404945628def6e608a61935951e4bc0d9
- Add plugin 'rmqtt-topic-rewrite'. https://github.com/rmqtt/rmqtt/commit/3ca34613e468ea68d604c958b88d19b46feb5bbc
- Implement exclusive subscription. https://github.com/rmqtt/rmqtt/commit/ed268d61f062bcb0f308220e7d5b30f8c4ac1483
- Add config limit_subscription. https://github.com/rmqtt/rmqtt/commit/c5a17032eabfc2fc6302d38c7b1c8fd29988b04c
- Implementing the basic delayed publishing feature. https://github.com/rmqtt/rmqtt/commit/3e50c3fdbb06ca1f14a192ffcfb41fd3dc041069
- Raft nodes support specifying the listening address separately. https://github.com/rmqtt/rmqtt/commit/10dbce8dcc00cf181db61b2c1155909423e62201
- Fixed: Kick out the specified client. The API call was successful, but the response returned a 404 error. #81 https://github.com/rmqtt/rmqtt/commit/54cb5be0fee4f11480a60285b6d49c2716e6d389
- arm64 platform docker image support. #74