{{ $t('productDocDetail.guideClickSwitch') }}
{{ $t('productDocDetail.know') }}
{{ $t('productDocDetail.dontRemind') }}
6.11.3
{{sendMatomoQuery("Sangfor Cloud Platform (SCP)","Application Dependency Analysis")}}

Application Dependency Analysis

{{ $t('productDocDetail.updateTime') }}: 2025-12-17

Clarify the application types and importance levels of the business systems to be migrated, including loads, front-end web services, middleware, cache/queue servers, back-end databases, and other independent businesses.

Before business migration, map out the access relationships between the various business systems to be migrated. This helps determine the sequence for migrating and activating the systems. There may be scenarios where some businesses need to be migrated while others remain in the original environment. In such cases, it is crucial to ensure normal access between the migrated business systems and the original environment.

A black and white logo

AI-generated content may be incorrect.

1.For large application groups, applications should be classified according to their characteristics into monolithic applications, clustered applications, and database applications. Create application architecture diagrams to clarify the application structure and relationships.

2.For database-related business migration, after migration is completed, perform data integrity verification and business availability testing. During this process, ACL rules can be added via a distributed firewall to allow access only from test terminals. Once data correctness and business availability are confirmed, full access can be granted. This prevents new data from other terminals being written before full verification, which could make rollback impossible.