smart-mqtt v1.5.0 Cuts Enterprise Package Size by 57% by Dropping Netty

smart-mqtt v1.5.0 reduces the enterprise package from 29.3 MB to 12.6 MB (57 % smaller) by replacing the Redisson‑based Redis bridge with the lightweight Redisun client, adds stability fixes, updates pricing, and provides detailed upgrade and deployment instructions.

Three Knives
Three Knives
Three Knives
smart-mqtt v1.5.0 Cuts Enterprise Package Size by 57% by Dropping Netty

Release Highlights

smart-mqtt v1.5.0 is released. The enterprise edition package size decreased from 29.3 MB to 12.6 MB (≈57 % reduction). The Redis bridge plugin size decreased from 15.5 MB to 81 KB.

Core Changes

Enterprise‑grade slimming : full package reduced to 12.6 MB.

Core component refactor : custom Redis client framework Redisun replaces Redisson, shrinking the bridge plugin to 81 KB.

Stability improvements : multiple bug fixes and plugin optimizations.

Size Reduction Analysis

Overall reduction : 29.3 MB → 12.6 MB (57 %).

Redis bridge plugin : 15.5 MB → 81 KB (99.5 %).

Configuration method : unchanged (environment variables / system properties).

Core dependency : switched from Redisson to Redisun, a lightweight 68 KB JAR that depends only on smart‑socket.

Redisun Client

Ultra‑light design : JAR size 68 KB, minimal runtime footprint.

Performance : benchmark report indicates higher throughput than Redisson.

Generality : suitable for MQTT bridging and other Redis client scenarios.

Open‑source : Apache License; repository at https://gitee.com/smartboot/redisun and documentation at https://smartboot.tech/redisun.

Benchmark report : https://smartboot.tech/redisun/guides/benchmark/.

Upgrade Guide

Backup existing configuration.

Download the v1.5.0 distribution.

Validate plugin functionality in a test environment.

Deploy to production and monitor.

Technical Comparison

Full package size : v1.4.0 = 29.3 MB → v1.5.0 = 12.6 MB (57 % reduction).

Redis bridge plugin : v1.4.0 = 15.5 MB → v1.5.0 = 81 KB (99.5 % reduction).

Configuration method : unchanged (environment variables / system properties).

Core dependency : v1.4.0 used Redisson; v1.5.0 uses Redisun (lighter).

Additional Optimizations

Wildcard subscription issue fixed for specific scenarios.

Feature module upgraded to 1.3.2, enhancing micro‑service governance.

smart‑socket upgraded to 1.7.5, improving network communication stability.

Class‑loading optimizations accelerate smart-mqtt-maven-plugin local startup.

Download

GitHub Releases: https://github.com/smartboot/smart-mqtt/releases/tag/v1.5.0

Gitee Releases: https://gitee.com/smartboot/smart-mqtt/releases/v1.5.0

Docker Deployment

docker run --name smart-mqtt \
  -p 1883:1883 \
  -p 8083:8083 \
  -d smartboot/smart-mqtt:1.5.0

Quick Start Script

# 1. Download distribution
wget https://github.com/smartboot/smart-mqtt/releases/download/v1.5.0/smart-mqtt-1.5.0.jar

# 2. Create start.sh
cat > start.sh <<'EOF'
#!/bin/bash
dir=$(dirname "$0")
export SMART_MQTT_PLUGINS=${dir}/plugins
export BROKER_PORT=1883
export BROKER_HOST="0.0.0.0"
export BROKER_MAXPACKETSIZE=8192
java -jar smart-mqtt-1.5.0.jar
EOF

# 3. Make executable and run
chmod +x start.sh
./start.sh

Future Outlook

Continuous performance optimization.

Deeper cloud‑native support, especially Kubernetes.

Enhanced observability (metrics, tracing, logging).

Expansion of enterprise‑grade plugins.

Security hardening (authentication, access control).

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

backendJavacloud-nativepackage optimizationMQTTsmart-mqttRedisun
Three Knives
Written by

Three Knives

Every line of code you contribute to open source could help make the future better.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.