BlazingMQ on Ubuntu 24.04

Azure Streaming & Messaging

A distributed message queueing broker, bound to loopback and authenticated from the first message it carries.

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Overview

BlazingMQ is an open source distributed message queueing framework from Bloomberg, built around a high performance C++ broker. It gives applications durable, ordered queues with priority, fanout and broadcast delivery semantics, along with a command line client for publishing and consuming messages. Queues are file backed, so messages survive a broker restart, and a set of ready to use queue domains covering each delivery mode is configured out of the box.

It suits teams that need dependable application to application messaging with predictable latency, and anyone who wants a message broker they run and own inside their own cloud account rather than a hosted queueing service.

Why the cloudimg image

BlazingMQ has no prebuilt binary distribution: it must be compiled from source together with the BDE and NTF libraries, which is a long and involved build. cloudimg ships it already built from pinned upstream sources, with the broker and its client ready to run. It is also secure by default, where the stock broker is not. Upstream listens on every interface and lets anonymous clients through; here the listener is bound to loopback only and authentication is required, so anonymous connections are rejected outright. A unique username and password are generated on each virtual machine's first boot and written to a root only file, so no credential is shared or baked into the image, and a fail secure bootstrap gate stops the broker starting at all until that per-VM credential exists. The paired deployment guide covers reading your credentials, reaching the broker over an SSH tunnel and running your first publish and consume. Every deployment carries 24/7 support.

Common uses

  • Durable application to application messaging with priority, fanout and broadcast queues
  • A message broker you run and own inside your own cloud account
  • Decoupling services behind persistent queues that survive a restart