Application Integration

Running a Message Broker with Amazon MQ - Choosing Between ActiveMQ and RabbitMQ and Migration Patterns

Compare ActiveMQ and RabbitMQ selection criteria, explore migration patterns from on-premises, and learn about high-availability configurations. Also covers when to use SQS/SNS instead.

約 3 分で読めます

Amazon MQ's Role and How It Differs from SQS/SNS

Amazon MQ is a managed broker service for ActiveMQ and RabbitMQ. While SQS and SNS are AWS-native messaging services, MQ provides managed operation of industry-standard message brokers. For new applications, SQS/SNS is recommended. However, when existing applications depend on the JMS API, AMQP protocol, or complex routing rules (topic selectors, message filters), rewriting for SQS/SNS can be costly. MQ is designed to migrate these existing applications to AWS with no code changes.

Choosing Between ActiveMQ and RabbitMQ

ActiveMQ has strong affinity with the Java ecosystem, fully supports JMS 2.0, and handles up to 1,000 connections per broker. It is ideal for migrating Java EE and Spring Framework-based applications. It simultaneously supports multiple protocols including STOMP, MQTT, and OpenWire, making it useful as a bridge between IoT devices and enterprise applications. RabbitMQ natively supports AMQP 0-9-1 and features flexible routing through Exchanges and Bindings. It has rich client libraries for Python, Ruby, Go, .NET, and other languages, making it well suited for polyglot environments. A management UI is provided out of the box for monitoring queue status and message rates from a browser.

High Availability and Migration Patterns

ActiveMQ's active/standby configuration places two broker instances in different AZs, persisting messages on shared EFS storage. When the primary fails, the standby automatically takes over, with failover completing in tens of seconds. RabbitMQ's cluster deployment configures a 3-node cluster with queue mirroring to ensure message durability. For on-premises migration, you simply create an MQ broker and change the application's connection URL to the MQ endpoint. A common pattern is to connect on-premises to MQ via VPN or Direct Connect and incrementally migrate workloads. For more detailed coverage of Amazon MQ, related books on Amazon are a helpful resource.

Amazon MQ Pricing

Amazon MQ pricing consists of per-broker-instance hourly charges and storage. An ActiveMQ mq.m5.large costs approximately $0.288 per hour (about $207 per month), while a RabbitMQ mq.m5.large costs approximately $0.302 per hour (about $217 per month). Active/standby configurations double the instance cost. Storage costs approximately $0.10 per GB per month. Compared to SQS (approximately $0.40 per million requests), MQ is more expensive, so SQS/SNS should be the first choice for anything other than migrating existing message brokers.

Summary

Amazon MQ is a service for lift-and-shift migration of existing message brokers to AWS. It supports industry-standard protocols for ActiveMQ and RabbitMQ, enabling migration with no code changes. The key decision criterion is to choose SQS/SNS for new development and MQ for migrating existing applications.

Related Services

Amazon MQA fully managed message broker service supporting Apache ActiveMQ and RabbitMQAmazon SQSA fully managed message queuing serviceAmazon SNSA fully managed Pub/Sub messaging and notification service

Related Articles

Building an Apache Kafka Streaming Platform with Amazon MSK - Cluster Design and OperationsDesign a managed Apache Kafka cluster, learn when to choose MSK Serverless, and explore data integration patterns with MSK Connect.Managed Message Broker - Building Enterprise Messaging Infrastructure with Amazon MQLearn how to build managed message brokers with Apache ActiveMQ and RabbitMQ using Amazon MQ. This article covers migration strategies from on-premises messaging systems and when to choose MQ over SQS.Notification Design with Amazon SNS - Topic and Subscription PatternsLearn how to choose between Standard and FIFO topics, implement the SQS fan-out pattern, and use subscription filters for conditional routing.

More on This Topic

SaaS Data Integration with Amazon AppFlow - Connecting Salesforce, Slack, and Google AnalyticsSync data from Salesforce and Slack to S3 and Redshift with no code. Learn about event-driven triggers, PII masking, and secure transfers via PrivateLink.Automating Data Integration - Building a SaaS Integration Platform with Amazon AppFlowLearn about SaaS application data integration using Amazon AppFlow. This article explains how to connect external services like Salesforce, Slack, and Google Analytics with AWS services using no code, and build real-time or schedule-based data flows.Event-Driven Architecture - Building Loosely Coupled Systems with Amazon EventBridgeLearn how to build event-driven architectures using Amazon EventBridge.EventBridge Pipes Design Best Practices - Optimizing Filtering and Batch ProcessingLearn practical best practices for EventBridge Pipes filtering design, batch size optimization, error handling strategies, and cost efficiency improvements.Event Integration with Amazon EventBridge Pipes - Connection Patterns for Sources and TargetsLearn how to connect event sources like SQS, DynamoDB Streams, and Kinesis directly to targets, with filtering and enrichment steps in between.IoT Event Detection - Automatically Detecting and Responding to Device State Changes with AWS IoT EventsLearn how to monitor IoT device state and automate responses with AWS IoT Events. Covers detector models for defining state transitions, alarm features, and SNS/Lambda integration.Workflow Management - Running Apache Airflow as a Managed Service with Amazon MWAALearn about data pipeline orchestration with Amazon MWAA (Managed Workflows for Apache Airflow). This article covers setup, DAG management, and when to choose Step Functions instead.Managed Message Broker - Building Enterprise Messaging Infrastructure with Amazon MQLearn how to build managed message brokers with Apache ActiveMQ and RabbitMQ using Amazon MQ. This article covers migration strategies from on-premises messaging systems and when to choose MQ over SQS.

Similar Articles and Services

Managed Message Broker - Building Enterprise Messaging Infrastructure with Amazon MQLearn how to build managed message brokers with Apache ActiveMQ and RabbitMQ using Amazon MQ. This article covers migration strategies from on-premises messaging systems and when to choose MQ over SQS.Amazon MQA fully managed message broker service offering Apache ActiveMQ and RabbitMQ, enabling migration of existing messaging applications to the cloud with minimal code changesBuilding Pub/Sub Messaging with Amazon SNS - Fan-Out Patterns and FilteringLearn about topic-based messaging with SNS, subscription filters, and the SQS fan-out pattern for scalable event distribution.Notification Design with Amazon SNS - Topic and Subscription PatternsLearn how to choose between Standard and FIFO topics, implement the SQS fan-out pattern, and use subscription filters for conditional routing.