Real-time for IoT and browsers in one broker
MQTT 5, WebSocket, and REST in one appliance.
Sensors on MQTT, browsers on WebSocket, servers on REST — one Buzz broker handles all three and records every message.
The problem
IoT devices speak MQTT. Browsers don’t. Servers want REST. You end up running three different services and gluing them with your own bridge code. And when the bridge crashes at 2 a.m., you get paged.
Our answer
Buzz is a single binary fronting MQTT v5 over TCP, TLS, WebSocket, and WSS — with a REST publish endpoint, REST-driven user management, and async recording to SQL or NoSQL. Dynamic credentials mean no password files and no reboots.
Outcomes
- One broker for sensors, browsers, and servers
- Revoke a device in milliseconds via REST
- Every message captured to your database of choice
- No glue service between MQTT and browser clients
The pipeline
- 1
Devices connect on TCP/TLS
Your fleet uses standard MQTT 5 libraries. No special SDK.
- 2
Browsers connect on WebSocket
Dashboards use the same MQTT topics over `wss://` using the standard MQTT-over-WebSocket subprotocol.
- 3
Servers publish via REST
Backend jobs fire events with a single HTTP POST. No MQTT library required.
- 4
Messages record asynchronously
Buzz writes every message to Postgres, Mongo, Elasticsearch, or whatever you choose — without blocking the hot path.
Products in this pattern
The products that make the pattern work. Each is a Docker image; each slots into the same contract.
Buzz
Messaging
A standalone MQTT 5 appliance with dynamic user management via REST, native browser WebSocket access, and async database recording.
Switchboard
Messaging
A unified gateway fronting Centrifugo with REST publish/subscribe, message recording, and operational dashboards.
Related industries
Ship the blocks. Focus on the product.
Docker-ready microservices you can deploy in an afternoon. Learn one, use them all.