This guide uses common fund transfer and point accumulation scenarios from the finance industry to introduce the unitization features of SOFAStack. It walks you through planning the architecture, setting up the environment, developing and deploying unitized applications, directing traffic, and validating the results.
Prerequisites
A dual-data center environment is configured.
The following unitized products must be deployed in the environment: Application Load Balancer (ALB), Spanner unified gateway, middleware (MQ, MS, DTX, DBP, DST), Unitized Application Service (LHC), and Real-time Monitoring Service (RMS).
Overall flow
The overall flow is shown in the following figure.
Architecture planning: Plan the unitized technical and application architecture. The output includes deployment and application architecture diagrams. These diagrams guide developers and Operations and Maintenance (O&M) engineers in environment initialization and application refactoring.
Environment initialization: Initialize the unitized environment based on the architecture plan to prepare for publishing applications.
Develop unitized applications: Refactor traditional applications and configure their unitized features.
Build and publish applications: Use LHC to publish the locally developed unitized applications to deployment units in the dual data centers.
Validate the results: Based on the fund transfer and point accumulation scenarios, complete an operation such as a transfer or deposit. Then, go to the various product consoles to validate the unitization results.
Direct traffic: Use LHC to direct application-layer traffic. Adjust and issue sharding rules for the access and application layers to validate the accuracy of traffic and RPC routing.