How to Tackle Cross‑Region C‑C Interactions in E‑Commerce Multi‑Active Architecture

01 – Architecture Thinking

Multi‑active deployments dramatically increase system complexity, especially across data‑center regions, leading to performance loss, data‑consistency delays, and heightened fault‑tolerance challenges.

02 – What is C‑C Interaction?

C‑C (Consumer‑Consumer) interaction refers to cross‑region user interactions where each user’s data resides in a different data‑center, e.g., a buyer in East China and another in North China.

Example: an e‑commerce order placed by User A in the East‑China node and User B in the North‑China node; their subsequent payment‑by‑another‑user scenario creates a cross‑region transaction.

03 – E‑commerce C‑C Interaction

Typical scenario: “代付” (payment on behalf) where the payer and the payee belong to different regions, forming a C‑C interaction.

Technical Challenges

Performance optimization – use low‑latency protocols such as WebSocket or MQ and local‑first computation.

Cross‑unit state synchronization – adopt CRDT or OT techniques.

Data‑sync delay and cross‑region message latency.

Case Study: Payment‑on‑Behalf Flow

User A in the North‑China node places an order and initiates a payment‑on‑behalf request; User B (payer) resides in the East‑China node.

Order data is replicated to the East‑China node via DTS; the payment request is sent to a message consumer group in that node.

The consumer checks whether the order data has arrived; if not, it may trigger a warning, delay queue, or dead‑letter queue for manual intervention.

Once the order is present, a notification is sent to User B to complete payment.

Successful payment triggers a success message back to User A’s region; failure triggers a rollback notification.

Read the earlier “跨单元交互” article for deeper understanding.

04 – Challenges Summary

Data synchronization latency.

Cross‑region message latency.