Cloud Message Queue

The benefits of TDMQ for CMQ are well reflected in the distributed transactions of WeChat’s red packet system. The WeChat architecture team has integrated the message queue service into the red packet system to reduce the overheads of distributed transactions on the system. When fund crediting fails, the account system will continuously pull the corresponding message from the message queue service and retry this update operation, ensuring that the crediting message will never get lost and avoiding the drawbacks such as rollback upon crediting failure and frequent polling of the database.

TDMQ for CMQ supports authentication based on HTTPS plus key for message delivery and leverages multidimensional security protection of the platform to defend against network attacks and protect the privacy of your businesses. If it is used by multiple business departments in your company at the same time, and you want to control their permissions, it allows you to set fine-grained resource permission policies.

TDMQ for CMQ can be deployed in multiple AZs. You can synchronously (for strong consistency) or asynchronously (for eventual consistency) store message bodies based on your business characteristics. If the message queue data on the primary node are completely lost due to force majeure events, the recovery point objective (RPO) for the primary and secondary nodes is within 5 minutes. After the disaster recovery and failover are completed, data difference may exist. In this case, you can associate with other databases for data reconciliation. The finance-grade disaster recovery solution safeguards core businesses of WeBank and Tenpay.