Migrating from Azure Service Bus to a self-managed RabbitMQ cluster for compliance control and disaster recovery
Azure Service Bus
RabbitMQFIMC has a validated RabbitMQ architecture and migration plan addressing their compliance control requirements and DR architecture needs, with a clear path from QA validation to production cutover.
Overview
FIMC, 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 FIMC'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; migrating to 3-node RabbitMQ cluster; 1,300 msg/sec; 200KB message payloads; 20–24 CPU cores; warm schema replication for disaster recovery; staged rollout (QA open-source, production 2027).
Approach
AceMQ architected the target RabbitMQ deployment: a 3-node cluster with 20–24 cores, message persistence configuration for 200KB payload handling, and a warm schema replication disaster recovery model. The migration uses a staged rollout — validating open-source RabbitMQ in QA before the planned 2027 production cutover.
Solution
- 13-node RabbitMQ cluster architecture sizing for 1,300 msg/sec at 200KB payloads
- 2Warm schema replication disaster recovery design
- 3Staged rollout plan: QA open-source validation before 2027 production migration
- 4Azure Service Bus to RabbitMQ messaging pattern translation
- 5Compliance control documentation for data handling requirements
- 6AceMQ commercial support agreement for production operations
Outcome
FIMC has a validated RabbitMQ architecture and migration plan addressing their compliance control requirements and DR architecture needs, with a clear path from QA validation to production cutover.
Technologies
Azure Service BusRabbitMQRelated Use Cases
Microsoft Service Bus to RabbitMQ Migration for Banking
Bank Vrede, dissatisfied with Microsoft Azure Service Bus performance and flexibility, engaged AceMQ to assess migration to RabbitMQ, comparing total cost, operational control, and messaging capability for banking workloads.
Azure Service Bus vs. RabbitMQ Cost and Architecture Comparison
AceMQ's Azure Service Bus comparison assessment helps organizations evaluate whether managed Azure messaging is cost-effective versus self-managed RabbitMQ with commercial support, covering both Standard and Premium tier economics.
Have a Azure Service Bus Challenge Like This?
AceMQ's senior Azure Service Bus engineers have handled this exact type of engagement before. Whether you need architectural guidance, hands-on remediation, or an ongoing managed partnership, we're ready to help.