Overview
Bank Vrede was experiencing limitations with Microsoft Azure Service Bus that impacted their banking messaging workloads. Dissatisfied with the constraints of the managed service model, they engaged AceMQ to evaluate whether migrating to self-managed RabbitMQ would provide better capabilities at a lower total cost.
Challenge
Azure Service Bus's managed service model limits the configurability available to banking organizations with specific routing, ordering, and message lifecycle requirements. Bank Vrede found that Azure Service Bus's constraints were forcing workarounds in their banking applications that would not be necessary with a more configurable messaging platform.
Environment
Azure cloud; Azure Service Bus; banking workloads with specific routing and ordering requirements.
Approach
AceMQ performed a structured comparison of Azure Service Bus and RabbitMQ capabilities against Bank Vrede's specific banking messaging requirements, including routing flexibility, message TTL control, dead letter handling, and total cost of ownership. The assessment produced a migration recommendation with implementation roadmap.
Solution
- Azure Service Bus vs. RabbitMQ capability comparison for banking workloads
- Routing, ordering, and message lifecycle requirement mapping
- Total cost of ownership comparison including Azure Service Bus fees vs. RabbitMQ + AceMQ support
- Migration architecture design for identified workloads
Outcome
Bank Vrede received a comprehensive capability and cost comparison supporting their migration decision, with AceMQ positioned to provide the commercial support model needed for banking-grade RabbitMQ operations.
Technologies
Azure Service Bus
RabbitMQ
Kafka
Docker
WSO2
