Message Broker Support Options Compared

RabbitMQ is open source, stewarded by Broadcom, which also sells the commercial distribution, Tanzu RabbitMQ. The project patches only its newest release series, so most production estates are on versions with no upstream fixes. Support for those comes from a Tanzu subscription or from an independent provider. AceMQ supports both, on any version, and is Broadcom's strategic RabbitMQ partner.

The Apache Kafka project offers mailing lists, not a contract. Confluent supports its own platform and cloud. AWS supports Amazon MSK as a service, which means the infrastructure, not your partitions, consumers or clients. An independent provider covers Apache Kafka as released, plus Confluent Platform and MSK estates, without requiring a platform subscription.

IBM supports IBM MQ through Subscription and Support for five years from a release's general availability, then sells Extended Support for up to four more. Only IBM can fix a product defect. An independent provider covers what the entitlement does not: the pager, configuration, performance, upgrades and migration.

Apache ActiveMQ has no vendor, and Classic and Artemis are now separate Apache projects. Red Hat supports its AMQ Broker distribution and AWS supports brokers inside Amazon MQ. For the Apache release on your own servers, support comes from an independent provider.

Pulsar is an Apache project with a commercial company, StreamNative, behind a platform and cloud service. Its operational weight is in BookKeeper and ZooKeeper, which is where most incidents start. Redpanda is a single-vendor product supported by Redpanda Data under an enterprise subscription. For both, an independent provider adds round-the-clock operational cover and a second opinion that is not selling you the platform.

With a cloud messaging service the provider runs the broker, and its support plan covers the service: availability, limits, billing. It does not cover how your application uses it. Lock expiry and dead-letter growth on Service Bus, visibility-timeout duplicates and FIFO limits on SQS, ordering keys and redelivery on Pub/Sub are all on your side of the line. That is the part an independent provider supports.

Ask two questions. Does a vendor exist for the exact thing you run? If you run the Apache or open-source release, usually not, and an independent contract is the only production support available. And who holds the pager? Vendor support fixes the product. It rarely knows your estate. If nobody on your team has run this broker through a serious incident, you need the second kind of support whether or not you have the first. One provider across several brokers also removes the hand-off when an incident crosses from one system to another.