Overview
A financial services organization is planning a migration from Azure Service Bus to a self-managed RabbitMQ cluster. The driver is a combination of compliance control requirements, disaster recovery architecture needs, and total cost management that Azure Service Bus's managed model does not accommodate.
Challenge
Azure Service Bus provided convenient managed messaging, but the firm's compliance requirements demanded greater control over data handling and disaster recovery configuration. The workload profile — 1,300 msg/sec with 200KB message payloads — required a carefully sized RabbitMQ cluster to match Azure Service Bus's throughput with comparable reliability.
Environment
Azure cloud; Azure Service Bus production; planned move to a 3-node RabbitMQ cluster; 1,300 msg/sec; 200KB message payloads; 24 CPU cores; warm schema replication for disaster recovery; proposed staged rollout (QA open-source first, production planned for 2027).
Approach
AceMQ proposed a target RabbitMQ deployment: a 3-node cluster with 24 cores, message persistence configuration for 200KB payload handling, and a warm schema replication disaster recovery model. The proposed migration uses a staged rollout — validating open-source RabbitMQ in QA before a planned 2027 production cutover.
Solution
- 3-node RabbitMQ cluster architecture sizing for 1,300 msg/sec at 200KB payloads
- Warm schema replication disaster recovery design
- Staged rollout plan: QA open-source validation before 2027 production migration
- Azure Service Bus to RabbitMQ messaging pattern translation
- Compliance control documentation for data handling requirements
- Proposed AceMQ commercial support for production operations
Outcome
AceMQ has proposed a RabbitMQ architecture and staged migration plan addressing the firm's compliance control requirements and DR architecture needs, with a path from QA validation to production cutover.