On this page
What this page is
These are AceMQ case studies for RabbitMQ, Kafka and Redis, drawn from work we have already published on our use-case pages. American National Insurance is the named reference for IBM MQ and Kafka migrations. Every summary below is taken from its case page, and every card links to the full account.
Named reference: American National Insurance
American National Insurance is the customer we name. Both descriptions stay within what the linked case pages say.
Insurance · IBM MQ to RabbitMQ
American National Insurance: phased IBM MQ to RabbitMQ migration
AceMQ led the phased migration of American National Insurance's IBM MQ infrastructure to RabbitMQ, including legacy code refactoring and HIPAA-compliant data handling across Windows and mainframe queue environments. Windows-based queues moved first, and the mainframe migration roadmap was defined and validated. The phased approach maintained operational continuity while progressively eliminating IBM MQ licensing costs.
Insurance · Kafka to Debezium and RabbitMQ
American National Insurance: Debezium and RabbitMQ chosen over Kafka
American National Insurance needed SQL Server change data capture and judged Kafka too complex to run for it. AceMQ designed a standalone Debezium Server and RabbitMQ architecture instead, keeping operations lean and message routing flexible.
RabbitMQ case studies: payments, aviation, energy and more
RabbitMQ is where most of our work sits, so most of the cases are RabbitMQ. The accounts are anonymised, and the table keeps the descriptor each case page uses.
| Account, as published | Industry | Technology | What was done |
|---|---|---|---|
| Fortune 500 Financial Services Company | Financial services / payments | RabbitMQ | Improving RabbitMQ reliability, queue behavior, and operational guidance for a payment system processing over 200 production changes weekly. Read the case |
| Global Aviation Technology Provider | Aviation / airport technology | RabbitMQ on Kubernetes | Troubleshooting cluster failover, partition handling, and quorum queue issues in a high-stakes aviation operational environment. Read the case |
| North American Pipeline Operator | Energy / utilities | RabbitMQ | Remediating critical RabbitMQ federation failures and implementing CVE patching across SCADA pipeline infrastructure where delays trigger mandatory shutdowns. Read the case |
| Fortune 500 Industrial Conglomerate | Industrial / manufacturing | RabbitMQ | Providing private CVE patching and remediation for legacy RabbitMQ versions across regulated industrial automation environments where forced upgrades are infeasible. Read the case |
| Global Automotive Manufacturer | Manufacturing / automotive | RabbitMQ, MQTT, Kafka | Replacing fragile SQL-trigger-based ingestion with a reliable event-driven architecture for plant-floor data movement and low-latency operations. Read the case |
| Fortune 500 Software Company | Software / digital platforms | RabbitMQ on AWS | Migration to supported RabbitMQ versions with managed services, standardization, compliance posture, and Tanzu commercial licensing. Read the case |
| State-Run Virtual Education Platform | Education | RabbitMQ | Standardizing RabbitMQ deployment and training staff while migrating infrastructure from VMware to Nutanix. Read the case |
Kafka and Redis case studies
The Kafka and Redis cases below are published as service use cases on our use-case pages.
| Account, as published | Industry | Technology | What was done |
|---|---|---|---|
| European Hosting Provider | Software / digital platforms | Apache Kafka | A five-node Kafka cluster serving 60,000 customers was timing out producers under load. The cause was topology, not capacity. Read the case |
| Real-Time Screen-Sharing SaaS Platform | Software / digital platforms | Redis | Six live sessions over fourteen hours to find why a Redis cluster kept growing past its ceiling, and to stop it without a maintenance window. Read the case |
The full library, filterable by technology and industry, is on the use cases page.
How to read these case studies
- Descriptors, not logos. Anonymised accounts keep the wording their case page uses. We publish no customer logos or quotes here.
- Each summary is the case page's own. Open the case for the challenge, approach and outcome in full.
- Outcomes are specific to the environment. A case shows what was done for one estate, not a guarantee for yours. A health check of 1 to 4 weeks, depending on complexity, is how we scope your own.
- Not included: engagements the use-case library lists as opportunities rather than delivered work.
Frequently asked questions
Does AceMQ publish customer case studies?
Yes. The use-case library holds the full accounts, and this page summarises eleven of them: two for American National Insurance, the named reference, and nine for anonymised accounts, covering RabbitMQ, Kafka and Redis.
Which AceMQ customers can be named?
American National Insurance. Other accounts are described by industry and size only, in the same words as their case pages.
How many customers does AceMQ have?
AceMQ supports 160+ enterprise customers across 26 countries.
Is there a RabbitMQ case study for IBM MQ migration?
Yes. American National Insurance moved IBM MQ workloads to RabbitMQ in phases, Windows-based queues first with a validated roadmap for the mainframe queues, under HIPAA requirements. The case page has the full account.