Apache RocketMQ
A distributed cloud-native messaging and streaming platform for building event-driven applications with low latency and high reliability.
What is Apache RocketMQ?
Apache RocketMQ is a distributed messaging and streaming platform that enables developers to build event-driven applications. It solves the problem of handling high-volume, low-latency message processing with financial-grade reliability and trillion-level scalability. The platform supports various messaging patterns and integrates seamlessly with modern cloud and big-data ecosystems.
Developers and architects building scalable, event-driven microservices, real-time data pipelines, and IoT applications that require reliable, high-performance messaging.
Developers choose RocketMQ for its proven reliability in financial scenarios, massive scalability, and rich feature set including transactional messaging, built-in tracing, and multi-protocol support—all within a flexible, cloud-native architecture.
Overview
Apache RocketMQ is a cloud native messaging and streaming platform, making it simple to build event-driven applications.
Use Cases
Best For
- Building high-throughput event-driven microservices architectures
- Processing financial transactions requiring guaranteed message delivery
- Handling IoT device messaging with MQTT and other protocols
- Creating real-time data streaming pipelines with big-data ecosystems
- Deploying scalable message queues in cloud-native Kubernetes environments
- Implementing ordered message processing for strict sequencing requirements
Not Ideal For
- Small-scale projects with minimal messaging needs where lightweight brokers like Redis Pub/Sub would suffice
- Teams wanting fully-managed, serverless messaging without infrastructure management overhead
- Environments where non-JVM language stacks dominate and native client support is limited
- Rapid prototyping scenarios requiring instant setup with zero configuration
Pros & Cons
Pros
Provides transactional messaging and built-in fault tolerance with DLedger Controller, ensuring message integrity for critical operations like financial transactions.
Handles trillion-level message capacities and million-level accumulation per queue, supporting high-throughput event-driven architectures as emphasized in the README.
Compatible with gRPC, MQTT, JMS, and OpenMessaging, making it adaptable for diverse use cases from microservices to IoT, as listed in the features.
Offers connectors for big-data systems, a Kubernetes operator, and an administrative dashboard, streamlining deployment and monitoring in modern cloud environments.
Cons
Setting up involves multiple components (NameServer, Broker) with detailed steps for local, Docker, and Kubernetes deployments, indicating a steep learning curve for newcomers.
Requires JDK 8 or higher and has a strong Java foundation, which may alienate teams using other technology stacks despite community clients in other languages.
The plethora of features like message filtering, tracing, and HA options demands significant tuning and expertise, slowing down initial implementation compared to simpler brokers.
Frequently Asked Questions
Related Projects
Apache Kafka StreamsApache Kafka - A distributed event streaming platform
nsqA realtime distributed messaging platform
NATS (k)High-Performance server for NATS.io, the cloud and edge native messaging system.
EMQ XThe most scalable and reliable MQTT broker for AI, IoT, IIoT and connected vehicles
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.