The transaction engine is the core system of Tencent billing. The data of each transaction order needs to be monitored by dozens of downstream business systems, including item price approval, delivery, reward point, and stream computing analysis. Such systems use different message processing logic, making it impossible for a single system to adapt to all associated business. In this case, TDMQ for Apache Pulsar can implement efficient async communication and application decoupling to ensure the business continuity of the primary site.
Peak Shifting
Companies hold promotional campaigns such as new product launch and festival red packet grabbing from time to time, which often cause temporary traffic spikes and pose huge challenges to each backend application system. In this case, TDMQ for Apache Pulsar can act as a buffer to centrally collect the suddenly increased requests in the upstream, allowing downstream businesses to consume the request messages based on their actual processing capacities.
Sequential Message Sending/Receiving
Sequential messages are used in some business scenarios, such as order creation, payment, delivery, and refund of in-app/game items, which are all strictly executed in sequence. Similar to the First In, First Out (FIFO) principle, TDMQ for Apache Pulsar offers a sequential message feature dedicated to such scenarios to ensure message FIFO.
Data Sync
TDMQ for Apache Pulsar can easily implement cross-IDC sync if messages need to be consumed across many IDCs.
Big Data Analysis
Data creates value in the "flow". Most traditional data analysis are based on batch computing models, which means they cannot analyze data in real time. In contrast, TDMQ for Apache Pulsar can easily implement real-time analysis of business data when combined with a stream computing engine.
