For hobbyists or small projects still on jabsubcom 2.x with fewer than 1,000 subscribers, the new version may be overkill. However, consider upgrading solely for the security patches.
broker: endpoint: 127.0.0.1:61613 transport: http3 # or tcp limits: max_subscribers_per_topic: 50000 distributed_hash_ring_size: 256 Legacy plain TCP on port 5555 is gone. All connections require TLS or WebSocket Secure (WSS). Performance Benchmarks: Jabsubcom New vs. Legacy Real-world tests on AWS c5.4xlarge instances (16 vCPU, 32GB RAM) with 5,000 simulated publishers and 20,000 subscribers:
openssl req -x509 -newkey ec -pkeyopt ec_paramgen_curve:P-256 \ -keyout server.key -out server.crt -days 365 \ -addext "extendedKeyUsage = serverAuth,clientAuth" Cause : The DSG recalculates preference lists every 30 seconds by default. Fix : Adjust rebalance_interval_sec in jabsubcom.yaml to 120 seconds for stable clusters. Issue 3: Legacy clients fail with "unsupported transport" Cause : Removed plain TCP support. Workaround : Deploy the jabsubcom-legacy-bridge container, which translates TCP to WebSocket Secure. This is officially supported until June 2026. Real-World Use Cases Benefiting from Jabsubcom New Several organizations have already migrated to jabsubcom new in beta. Notable examples: jabsubcom new
wget https://repo.jabsubcom.io/releases/jabsubcom-new-3.0.0.tgz tar -xzf jabsubcom-new-3.0.0.tgz cd jabsubcom-new ./bin/init-cluster --mode distributed --nodes 3 Warning : A rolling upgrade is not supported; you will experience downtime of approximately 2–5 minutes.
curl -sSL https://jabsubcom.io/check-upgrade | bash : Jabsubcom new is not just an incremental update; it is a future-proofing move for any organization serious about real-time messaging at scale. Have you deployed jabsubcom new in production? Share your experiences in the comments below, or report issues on their GitHub tracker. For hobbyists or small projects still on jabsubcom 2
To get started, visit the official migration guide at jabsubcom.io/new-migration or run the automated readiness checker:
| Metric | Jabsubcom 2.6.4 | Jabsubcom New (3.0.0) | Improvement | |--------|----------------|----------------------|--------------| | Publish latency (p99) | 42 ms | 18 ms | 57% better | | Subscription handshake time | 110 ms | 34 ms | 69% better | | Max throughput (msgs/sec) | 85k | 210k | 147% increase | | Rebalance time after node failure | 45 sec | 3.2 sec | 14x faster | | Memory footprint (idle) | 1.8 GB | 2.4 GB | Regression (33% higher) | All connections require TLS or WebSocket Secure (WSS)
jabsubcom.broker.host=127.0.0.1 jabsubcom.broker.port=61613 jabsubcom.max.subscribers=10000