Question

A financial services company runs a monolithic on-premises Java application that relies heavily on a self-managed RabbitMQ cluster for asynchronous messaging between internal components. The company wants to migrate to AWS with minimal application code changes and no re-engineering of the messaging protocol. The messaging middleware must remain compatible with the existing AMQP 0-9-1 clients, and the operations team wants AWS to handle broker patching, high availability, and automated failover across Availability Zones. Which approach best meets these requirements with the least migration effort?

Accepted Answer

Migrate the messaging layer to Amazon MQ for RabbitMQ deployed in a cluster deployment mode across multiple Availability Zones.

Answer

Refactor the application to publish and consume messages using Amazon SQS standard queues and Amazon SNS topics for fan-out.

Answer

Deploy RabbitMQ on a self-managed Amazon EC2 Auto Scaling group with an Application Load Balancer in front of the broker nodes.

Answer

Replatform the messaging layer to Amazon Kinesis Data Streams and update the application to use the Kinesis Client Library.