The global message backup feature allows you to back up messages in one-way backup mode and two-way backup mode. The two modes are commonly used in the following scenarios: data aggregation, geo-disaster recovery, and active geo-redundancy. This topic describes the business architectures used in the preceding scenarios.
Data aggregation (one-way backup mode)
Business deployed in each independent unit (business environment) is processed on the server that is closest to the unit without cross-network data access. This prevents timeout issues caused by networks. In this scenario, data can be aggregated to the central unit by using the one-way backup mode supported by the global message backup feature. This way, the central region can process the aggregated data in a unified manner.
Industries: banking, securities, insurance, and others
Architecture: Multiple units and one center
Figure 1. Architecture for data aggregation in ApsaraMQ for RocketMQ
Geo-disaster recovery (one-way backup mode)
The one-way backup mode supported by the global message backup feature can help implement cross-region high availability to improve data security and system availability. When faults occur in a data center or a region, you can use the one-way backup mode to quickly restore business.
Industries: all
Architecture: two regions and two data centers
Figure 2. Architecture for geo-disaster recovery in ApsaraMQ for RocketMQ
In normal cases, you do not need to run applications in the secondary region or center. This helps reduce resource consumption and save costs. If an exception occurs, you can start the applications in the secondary region or center and use the consumer offset resetting feature of the ApsaraMQ for RocketMQ instance to consume a minimum number of historical messages. We recommend that you perform message idempotence to reduce business impacts caused by message duplication.
Active geo-redundancy (two-way backup mode)
If you want to deploy your business in multiple units and ensure business continuity at the same time, you can use the two-way backup mode supported by the global message backup feature to implement cross-region high availability.
Industries: finance, energy and other industries related to the livelihood of people
Architecture: two regions and two data centers
Figure 3. Architecture for active geo-redundancy in ApsaraMQ for RocketMQ
When you use the global message backup feature to synchronize data, tags are added to messages. This way, no extra development is required for producer applications, and consumer applications can consume messages that contain specific tags by using the SQL-92 filtering method provided by ApsaraMQ for RocketMQ.
If an exception occurs, the disaster-recovery capabilities of the business can ensure that the overall business runs as expected. In this case, producer applications can receive all messages and deliver the messages to the ApsaraMQ for RocketMQ instance on which no exceptions occur. However, you must modify the filtering conditions on the consumer applications. You can use the consumer offset resetting feature of the ApsaraMQ for RocketMQ instance to consume a minimum number of messages from other regions. We recommend that you perform message idempotence to reduce business impacts caused by message duplication.