Application Version Switching via Link File Redirection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing application systems face high I/O loads, making it difficult to perform file operations efficiently and quickly switch between application versions, especially during high concurrency and high I/O loads.
Innovation Solution
The method involves creating storage paths for multiple versions of an application, using link files to point to these paths, and switching between them by deleting and recreating link files, allowing for quick version switching without limitations on frequency or time, even in high concurrency and high I/O conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If traditional file operation methods are used for application version switching, then version switching can be performed, but the I/O load becomes very high and file operations cannot be performed efficiently
Solution Approach 1:
The patent segments the file system into multiple versioned directories (e.g., /app/v1, /app/v2) where each directory stores a complete version of the application files. This segmentation allows the system to switch between versions by simply changing which directory is active, rather than performing file operations across a single shared filesystem, thereby reducing I/O load and enabling efficient version switching.
Solution Approach 2:
The patent introduces a version management mechanism that acts as an intermediary between the application and the underlying file system. This mechanism handles version switching by managing symbolic links or mount points that point to different version directories, abstracting away the complex file operations and reducing the I/O burden on the underlying storage system.
2Reliability
If application version switching is performed under high concurrency and high I/O load conditions, then version rollback is needed, but the high I/O load prevents efficient file operations
Solution Approach 1:
The patent performs preliminary actions by pre-organizing all application versions in dedicated directories before any switching is needed. Each version is fully prepared and stored in its own directory (e.g., /app/v1, /app/v2), so that when version rollback is needed, the system can immediately switch to the desired version without performing any file copy or migration operations, ensuring reliable version recovery even under high load conditions.
Solution Approach 2:
The patent uses symbolic links (a form of copying reference) to create lightweight references to version directories. Instead of physically copying files during version switching, the system uses symbolic links that point to the appropriate version directory, enabling fast and reliable version switching without the I/O overhead of actual file copying, thus maintaining file operation throughput even during version rollback.
3Adaptability or versatility
If frequent version switching is performed to manage application versions, then version flexibility is improved, but the frequency of file operations increases the I/O load
Solution Approach 1:
The patent extracts the version identification information from the file operations themselves and places it at the directory level. By organizing files into versioned directories and using symbolic links to point to these directories, the system separates the version management logic from the actual file access operations. This allows frequent version switching to be achieved by simply changing the symbolic link target, not by performing repeated file operations, thus maintaining high adaptability while preserving file system I/O capacity.
Data Source
AI summary
The present disclosure relates to an application version switching method comprising: creating storage paths for at least two versions of an application; creating a first link file for a currently used version of the application, wherein the first link file points to a storage path for the currently used version of the application; acquiring an application version switching instruction; and if a storage path for a target switching version of the application exists, deleting the first link file, and creating a second link file for the target switching version of the application, wherein the second link file points to the storage path for the target switching version of the application. The present disclosure also relates to an application version switching apparatus, an electronic device and a storage medium.