TDMQ for RabbitMQ is fully compatible with the AMQP 0-9-1 protocol and the open-source RabbitMQ client. The business code requires no modification to be smoothly migrated to the cloud, aiming to provide users with a more stable and reliable message queue service.
Open-Source Compatibility and Out-of-the-Box
It supports the out-of-the-box feature and one-click automatic cluster creation, eliminating the need for manual installation and deployment. It is compatible with the AMQP 0-9-1 protocol and the open-source RabbitMQ client, allowing hitless cloud migration without any business code modifications. Various specifications are provided for selection, enabling users to flexibly scale in the console without the need to pay attention to underlying resources.
Enhanced Observability
It provides comprehensive monitoring and alarm capabilities, covering multi-dimensional metrics such as clusters, nodes, vhosts, exchanges, and queues, helping you monitor the running status of the cluster in real time. Message query and message trace capabilities are supported simultaneously, clearly displaying the complete lifecycle of messages, facilitating rapid issue location, and improving Ops efficiency.
High Availability and Reliability
Architecture upgrades of it has effectively addressed common stability issues found in the open-source version, such as message backlogs and split-brain. It employs a multi-AZ distributed deployment architecture, enabling automatic disaster recovery failover to easily handle IDC-level faults, and guarantees service availability with an SLA of no less than 99.95%. Additionally, it adopts a three-replica data persistence mechanism to ensure reliable and persistent message data.
Flexible Adaptation to Multiple Business Scenarios
It provides multiple routing methods, such as direct, fanout, topic, header, and x-delayed-message, allowing flexible combinations of exchange types to meet complex business requirements. It also supports various message types, such as broadcast messages, delayed messages, and dead letter queues, catering to the requirements of typical scenarios such as order timeout handling, event notifications, and asynchronous decoupling, delivering a highly flexible message solution.