Distributed file sharing method and device capable of shielding different technology types, storage medium and electronic equipment

Abstract

The embodiment of the invention provides a distributed file sharing method and device capable of shielding different technical types, a storage medium and electronic equipment, and relates to the technical field of file sharing, the method comprises the following steps: reading a configuration file of a business service to obtain a specific shared storage type; performing unified interface initialization on the universal interfaces of different shared storage types; for shared storage type selection with a storage network protocol, creating a connection pool of distributed shared storage; constructing a unified universal access interface by adopting a facade mode; and the business service completes file sharing based on the universal access interface and the connection pool. According to the method, a unified file sharing access mode can be provided for business services, file access is changed from a network mode to a local access mode, a business system does not need to pay attention to specific storage type selection, non-inductive switching and deployment of different storage technology type selection of different platforms are achieved, and development, operation and maintenance efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of file sharing, in particular to a distributed file sharing method and device capable of shielding different technical selections, a storage medium and an electronic device. BACKGROUND

[0002] With the increasing degree and scale of cloud platform informatization construction, the range of informatization construction has been extended from equipment in space to ground mobile vehicles / stations, and has not been limited to the traditional server room plus PC client scenario. Due to specific conditions, the technical system adopted by the cloud platform will be different in different scenarios. At the same time, there is also a problem of different technical systems between new and old systems that cooperate with each other in the case of technical upgrading. Based on the above actual situation, the technical systems of different cloud platforms in different scenarios are quite different. The information system based on the cloud platform often contains multiple types of business application services, and the existing business application services usually only select one technical system for targeted development during the development process. If the cloud platform technical selection is not determined or changes, it will bring a lot of work to modify the code for the development and operation of business services, and increase the maintenance difficulty.

[0003] Especially in the field of space information systems, a large amount of information is stored and interacted in the form of files. The technical selection of distributed file sharing storage is typically ftp, sftp, local disk storage, OSS object storage, NAS storage, open source minio, and the like. The sharing method of files includes ftp protocol, sftp protocol, http protocol, NFS protocol, webservice protocol, and the like. The cloud platform stores the above-mentioned business file storage and sharing methods in different business and deployment scenarios. There may be code level switching of file interaction methods and corresponding testing and verification in different stages of development, deployment and operation. The code development efficiency is low, and the corresponding difficulty is brought to the code maintenance. SUMMARY

[0004] Embodiments of the present application provide a distributed file sharing method and device capable of shielding different technical selections, a storage medium and an electronic device to solve the technical problems in the background art.

[0005] Other characteristics and advantages of the present application will become apparent from the following detailed description, or will be learned by practice of the present application.

[0006] According to a first aspect of the embodiments of the present application, a distributed file sharing method capable of shielding different technical selections is provided, comprising: reading a configuration file of a business service to obtain a specific shared storage selection; performing unified interface initialization on the universal interface of different shared storage selections; For the shared storage option with a storage network protocol, a connection pool of distributed shared storage is created; A unified general access interface is constructed using a facade mode; Business services complete file sharing based on the general access interface and the connection pool.

[0007] In some embodiments of the present application, based on the foregoing scheme, the shared storage option includes: ftp, sftp, local disk storage, OSS object storage, NAS storage, and open source minio.

[0008] In some embodiments of the present application, based on the foregoing scheme, the unified interface initialization of the general interface of different shared storage options includes: The initialized interface implementation class is used to initialize the general interface implementation class of the shared storage option, and the initialized interface implementation class is injected into the service class required by the business application to use file sharing storage.

[0009] In some embodiments of the present application, based on the foregoing scheme, the storage network protocol includes: ftp protocol, sftp protocol, http protocol, NFS protocol, and webservice protocol.

[0010] In some embodiments of the present application, based on the foregoing scheme, the unified general access interface is constructed using a facade mode, including: The facade mode is used to abstract a unified usage from various shared scenarios of business files, as a file sharing method; The file sharing method is encapsulated into a unified general access interface.

[0011] In some embodiments of the present application, based on the foregoing scheme, the usage includes: single or batch file upload, single or batch file download, file query, file storage path query, file deletion, and file directory creation.

[0012] In some embodiments of the present application, based on the foregoing scheme, the business services complete file sharing based on the general access interface and the connection pool, including: The business service transmits relevant file operation parameters according to the parameter requirements of the general interface; According to the shared storage option configured by the business service, a connection with the distributed shared storage is obtained from the connection pool; According to the acquisition result, the validity of the file operation parameters transmitted by the business service is judged; In the case of judging as valid, the file operation parameters transmitted by the business service are converted according to the client interface parameter list requirements of the specific shared storage option; According to the converted file operation parameter, a client interface of a specific shared storage type is called to perform actual operation on the remote file; The result returned by the client interface of the specific shared storage type is checked and encapsulated according to the return value requirement of the general interface; After the file operation is successful, the connection is returned to the connection pool, and the file operation result is returned to the business service.

[0013] According to a second aspect of the embodiment of the application, a distributed file sharing device capable of shielding different technical types is provided, comprising: A reading unit is configured to read a configuration file of a business service to obtain a specific shared storage type; An initialization unit is configured to perform unified interface initialization on the general interface of different shared storage types; A creating unit is configured to create a connection pool of distributed shared storage for the shared storage type with a storage network protocol; A building unit is configured to build a unified general access interface by using a facade mode; A sharing unit is configured to complete file sharing by the business service based on the general access interface and the connection pool.

[0014] According to a third aspect of the embodiment of the application, a computer readable storage medium is provided, the storage medium stores computer instructions, and the computer instructions make the computer execute the method of the first aspect when running on the computer.

[0015] According to a fourth aspect of the embodiment of the application, an electronic device is provided, comprising a memory and a processor; The memory is configured to store computer instructions; The processor is configured to call the computer instructions stored in the memory, so that the electronic device executes the method of the first aspect.

[0016] The method for the business service of the information system to share distributed files based on the cloud native platform provided by the application can provide unified file access and sharing under different storage schemes for the upper business service by adapting different distributed storage network protocols, and can shield the technical types of the bottom layer OSS object storage, local disk storage, NAS storage, FTP and other distributed storage for the business service. Compared with the existing business service development, the technical type is specific, and the following beneficial effects are obtained: Providing a unified access method for distributed file sharing and access, and shielding storage selection for various cloud platform information system business services deployed in different business scenarios, can allow R&D personnel to focus more on the research and development of business systems, avoid a large number of business applications adapting to different storage selections, and avoid the same business service being adapted and transformed one by one due to changes in the platform's underlying technology selection or changes in the operating platform, resulting in various different versions, low work efficiency, and difficulty in version maintenance. In addition, this method is scalable to adapt to various storage selections, and business application services only need to modify the configuration file to adapt to the selection change, avoiding code changes and adaptation of the business service itself. In the event of a specific storage selection change, the business application only needs to modify its own configuration file and restart the business service to complete a seamless switch, without the problem of maintaining multiple versions of business software.

[0017] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings are incorporated into and constitute a part of the specification, illustrating embodiments consistent with the present application and, together with the specification, explaining the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and those skilled in the art can derive other drawings based on these drawings without inventive effort. In the drawings: Figure 1 A schematic flow chart of a distributed file sharing method capable of shielding different technology selections according to an embodiment of the present application is shown; Figure 2 A schematic diagram of a distributed file sharing method capable of shielding different technology selections according to an embodiment of the present application is shown; Figure 3 A schematic diagram of a process of initializing an interface according to an embodiment of the present application is shown; Figure 4 A schematic diagram of a process for implementing file sharing according to an embodiment of the present application is shown; Figure 5 A block diagram of a distributed file sharing device capable of shielding different technology selections according to an embodiment of the present application is shown; Figure 6 A block diagram of an electronic device according to an embodiment of the present application is shown; Figure 7 A schematic diagram of the structure of a computer system suitable for implementing an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0019] Example implementations will now be described more fully with reference to the accompanying drawings. Example implementations can be implemented in any

[0020] Moreover, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the application. One skilled in the relevant art will recognize, however, that the

[0021] The block diagrams in the drawings show only the functionality of the embodiments and do not imply any particular physical or architectural arrangement of the devices, systems, or methods. No inference should be drawn regarding the

[0022] The flow diagrams depicted in the figures are merely exemplary and do not necessarily include all of the steps or operations, nor do they necessarily indicate the order in which the steps or operations can be performed. For example, some operations can be performed in parallel, some operations can be omitted, and some operations can be performed in a different order than depicted in the figures.

[0023] In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative effort belong to the protection scope of the present application.

[0024] Some embodiments of the present application will be described in detail below with reference to the drawings. The following embodiments and features in the embodiments can be combined with each other without conflict.

[0025] Referring to FIG. 1, a flow diagram of a distributed file sharing method capable of shielding different technical options is shown according to an embodiment of the present application. Figure 1

[0026] Referring to FIG. 1, a flow diagram of a distributed file sharing method capable of shielding different technical options is shown according to an embodiment of the present application. Figure 2 ​, shows a schematic diagram of a distributed file sharing method capable of shielding different technical options according to an embodiment of the application.

[0027] As shown in Figure 1 , a distributed file sharing method capable of shielding different technical options is shown, which specifically includes steps S100 to S500.

[0028] Referring to Figure 1 , in step S100, a configuration file of a business service is read to obtain a specific shared storage option.

[0029] In some possible embodiments, based on the foregoing scheme, the shared storage option includes ftp, sftp, local disk storage, OSS object storage, NAS storage, and open source minio.

[0030] Continuing to refer to Figure 1 , in step S200, a unified interface initialization is performed on the universal interface of different shared storage options.

[0031] It can be understood that the unified initialization of the universal interface ensures that various types of shared storage options can be connected.

[0032] In some possible embodiments, based on the foregoing scheme, step S200 includes: An initialized interface implementation class is used to initialize a universal interface implementation class of the shared storage option, and the initialized interface implementation class is injected into a service class required by a business application to use file sharing storage.

[0033] Exemplarily, referring to Figure 3 , a flowchart of interface initialization is shown.

[0034] As shown in Figure 3 , the initialization step includes: Step A1: the business service loads a configuration file; Step A2: the specific option of the shared storage in the business service configuration is read by the method; Step A3: according to the specific storage option, the universal interface provided by each different storage option is loaded; Step A4: the universal interface implementation class with a connection pool feature is initialized using the initialized interface implementation class; Step A5: the initialized interface implementation class is injected into a service class required by an application to use file sharing storage, and the initialization of the business service file access is completed.

[0035] Continuing to refer to Figure 1 , in step S300, for the shared storage option with a storage network protocol, a connection pool of distributed shared storage is created.

[0036] It should be noted that the step aims to build a logical access connection channel for the business service and the distributed storage.

[0037] In some possible embodiments, based on the foregoing scheme, the storage network protocol includes: an ftp protocol, an sftp protocol, an http protocol, an NFS protocol, and a webservice protocol.

[0038] With reference back to Figure 1 , step S400, a unified general access access interface is built using a facade mode.

[0039] In some possible embodiments, based on the foregoing scheme, step S400 includes: A unified usage mode is abstracted from various sharing scenarios of business files using a facade mode, as a file sharing mode; The file sharing mode is encapsulated into a unified general access access interface.

[0040] In some possible embodiments, based on the foregoing scheme, the usage mode includes: single or batch file upload, single or batch file download, file query, file storage path query, file deletion, and file directory creation.

[0041] With reference back to Figure 1 , step S500, the business service completes file sharing based on the general access access interface and the connection pool.

[0042] In some possible embodiments, based on the foregoing scheme, step S500 includes: The business service transmits relevant file operation parameters according to the parameter requirements of the general interface; According to the sharing storage selection configured by the business service, a connection to the distributed shared storage is obtained from the connection pool; According to the obtaining result, the validity of the file operation parameters transmitted by the business service is judged; In the case of judging as valid, the file operation parameters transmitted by the business service are converted according to the client interface parameter list requirements of the specific sharing storage selection; According to the converted file operation parameters, the client interface of the specific sharing storage selection is called to actually operate the remote file; The result returned by the client interface of the specific sharing storage selection is checked and encapsulated and converted according to the return value requirements of the general interface; After the file operation is successful, the connection is returned to the connection pool, and the file operation result is returned to the business service.

[0043] It can be understood that the file sharing mode through the step can change the file access from a network mode to a local access mode, and realizes shielding of a specific shared storage selection.

[0044] For example, refer to Figure 4 , a flowchart for realizing file sharing is shown.

[0045] As shown in Figure 4 , after the business service completes initialization shown in Figure 3 , the specific steps for realizing file sharing are as follows: Step B1: the business service transmits relevant file operation parameters such as file upload data and upload path according to the parameter requirements of the general interface; Step B2: according to the shared storage selection configured by the business service, a connection with the distributed shared storage is obtained from the connection pool, if the connection fails, the business service is directly returned with information of file operation failure; if the connection succeeds, the validity of the file operation parameters transmitted by the business service is judged; Step B3: if the file operation parameters transmitted by the business service fail the verification, the connection is returned to the connection pool, and the business service is returned with information of file operation failure; if the file operation parameters transmitted by the business service are valid, the file operation parameters transmitted by the business service are converted according to the client interface parameter list requirements of the specific shared storage selection; Step B4: according to the converted file operation parameters, the client interface of the specific shared storage selection is called to perform actual operation on the remote file; Step B5: the result returned by the client interface of the specific shared storage selection is checked and encapsulated and converted according to the return value requirements of the general interface, the returned result is divided into three categories: no return value, directly returned; success / failure, converted into a Boolean type after being determined; list type, converted and returned using a new set after traversal; Step B6: after the file operation succeeds, the connection is returned to the connection pool, and the business service is returned with the file operation result.

[0046] In summary, the distributed file sharing method provided by the application can provide a unified file sharing access mode for business services, change the file access from a network mode to a local access mode, let the business system not pay attention to the specific storage selection, realize the no-sensing switching and deployment of different platforms and different storage technology selections, and improve the development and operation efficiency. The method also has expansion capability, and can adapt to other new storage selections under the no-sensing experience of the business.

[0047] The device embodiment of the present application is introduced below, which can be used to execute the distributed file sharing method of different technology selection shielding type in the above-mentioned embodiments of the present application. For details not disclosed in the device embodiment of the present application, please refer to the above-mentioned embodiments of the method of the present application.

[0048] Referring to Figure 5 The device 500 of distributed file sharing of different technology selection shielding type according to one embodiment of the present application is shown in the figure, which comprises: A reading unit 501 is configured to read the configuration file of the service to obtain specific shared storage selection; An initialization unit 502 is configured to perform unified interface initialization on the general interface of different shared storage selection; A creating unit 503 is configured to create a connection pool of distributed shared storage for the shared storage selection with storage network protocol; A constructing unit 504 is configured to construct a unified general access interface by using facade mode; A sharing unit 505 is configured to complete file sharing by the service based on the general access interface and the connection pool.

[0049] As Figure 6 The present application further provides an electronic device 600, which comprises a memory 610, a processor 620, and a computer program 611 stored in the memory 610 and executable on the processor, and the processor 620 implements the steps of the above-mentioned distributed file sharing method of different technology selection shielding type when executing the computer program 611.

[0050] Since the electronic device introduced in the present embodiment is the device used to implement the distributed file sharing device of different technology selection shielding type in the embodiments of the present application, the specific implementation of the electronic device of the present embodiment and its various changes can be understood by those skilled in the art based on the method introduced in the embodiments of the present application, so the implementation of the method in the embodiments of the present application by the electronic device will not be introduced in detail, and the device used to implement the method in the embodiments of the present application by those skilled in the art belongs to the scope of the present application.

[0051] In the specific implementation process, the computer program 611 can implement any embodiment in the first aspect when executed by the processor.

[0052] Figure 7 The structure schematic diagram of the computer system of the electronic device suitable for implementing the embodiments of the present application is shown.

[0053] It should be noted that, Figure 7The computer system 700 of the illustrated electronic device is merely one example, and should not be taken as limiting the functionality or use of embodiments of the present application.

[0054] As shown in Figure 7 The computer system 700 includes a central processing unit (CPU) 701, which can perform various suitable actions and processes in accordance with a program stored in a read-only memory (ROM) 702 or a program loaded from a storage section 708 into a random access memory (RAM) 703, such as performing the methods described in the above embodiments. Various programs and data required for the operation of the system are also stored in the RAM 703. The CPU 701, the ROM 702, and the RAM 703 are connected to each other through a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0055] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, a mouse, etc.; an output section 707 including a display such as a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as necessary. A removable recording medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is attached to the drive 710 as necessary, so that a computer program read therefrom is installed into the storage section 708 as necessary.

[0056] In particular, in accordance with embodiments of the present application, the processes described above with reference to the flowcharts can be implemented as a computer software program. For example, embodiments of the present application include a computer program product comprising a computer program carried on a computer readable medium, the computer program comprising program code for performing the methods illustrated by the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via the communication section 709, and / or installed from the removable recording medium 711. When the computer program is executed by the central processing unit (CPU) 701, various functions defined in the system of the present application are performed.

[0057] It should be noted that the computer-readable medium in the embodiments of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination thereof. The computer-readable storage medium may, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination thereof. More specific examples of the computer-readable storage medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (Compact Disc Read-Only Memory, CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device or apparatus. In the present application, the computer-readable signal medium can include a data signal carried in a baseband or as a part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take various forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, which can send, transmit, propagate or transport a program for use by or in conjunction with an instruction execution system, device or apparatus. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, or the like, or any suitable combination thereof.

[0058] The flowcharts and block diagrams in the drawings illustrate the possible implementation architectures, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In the flowcharts or block diagrams, each block can represent a module, a program segment or a part of code, which contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur in different orders than that shown in the drawings. For example, two blocks that are shown in succession can actually be executed substantially in parallel, and sometimes in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams or flowcharts, and the combination of blocks in the block diagrams or flowcharts, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0059] The units described in the embodiments of the present application can be implemented by software, or can be implemented by hardware, and the units described can also be arranged in a processor. In some cases, the names of the units do not constitute a limitation on the units themselves.

[0060] As another aspect, the present application also provides a computer program product or computer program, which includes computer instructions stored in a computer readable storage medium. A processor of a computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device performs the distributed file sharing method capable of shielding different technology selections described in the above embodiments.

[0061] As another aspect, the present application also provides a computer readable medium, which can be included in the electronic device described in the above embodiments, or can exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to implement the distributed file sharing method capable of shielding different technology selections described in the above embodiments.

[0062] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, the division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided into several modules or units.

[0063] From the above description of the embodiments, those skilled in the art can easily understand that the example embodiments described herein can be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solutions according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) or network, and includes several instructions to make a computing device (which can be a personal computer, server, touch terminal, or network device, etc.) execute the methods according to the embodiments of the present application.

[0064] Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments disclosed herein. It is intended that the application embrace any and all variations of the application that fall within the scope of the general description herein. It is to be understood that the application is not to be limited to the specific examples, methods, and procedures described herein, and that specific examples are to be considered as illustrative only. It is further understood that the application can encompass all such variations as fall within the scope of the application. It is intended that the scope of the application encompass all techniques capable of approximating the teachings provided herein.

Claims

1. A distributed file sharing method capable of shielding different technology selections, characterized in that: include: Read the business service configuration file to obtain the specific shared storage selection; Perform unified interface initialization for common interfaces of different shared storage options; For shared storage options with storage network protocols, create a connection pool for distributed shared storage; Use the facade mode to build a unified universal access interface; The business service completes file sharing based on the universal access interface and the connection pool.

2. The method according to claim 1, characterized in that The shared storage options include: ftp, sftp, local disk storage, OSS object storage, NAS storage and open source minio.

3. The method according to claim 1, characterized in that The unified interface initialization for the universal interfaces of different shared storage options includes: Use the initialized interface implementation class to initialize the common interface implementation class for shared storage selection, and inject the initialized interface implementation class into the service class required by the business application to use the file shared storage.

4. The method according to claim 1, wherein The storage network protocols include: ftp protocol, sftp protocol, http protocol, NFS protocol and webservice protocol.

5. The method according to claim 1, wherein The unified universal access interface constructed using the facade mode includes: The facade pattern is used to abstract a unified usage method for various sharing scenarios of business files as a file sharing method; The file sharing method is encapsulated into a unified universal access interface.

6. The method according to claim 5, characterized in that The usage includes: single or batch file uploading, single or batch file downloading, file query, file storage path query, file deletion, and file directory creation.

7. The method according to claim 1, characterized in that The business service completes file sharing based on the universal access interface and the connection pool, including: The business service passes in relevant file operation parameters according to the parameter requirements of the general interface; Based on the shared storage type selected in the business service configuration, obtain a connection to the distributed shared storage from the connection pool; Determine the validity of the file operation parameters passed to the business service based on the obtained results; If the result is valid, the file operation parameters passed to the business service are converted according to the client interface parameter list requirements of the specific shared storage selection; Based on the converted file operation parameters, the client interface of the specific shared storage type is called to perform actual operations on the remote file. The results returned by the client interface of the specific shared storage selection are checked and encapsulated according to the return value requirements of the general interface; After the file operation is successful, the connection is returned to the connection pool and the file operation result is returned to the business service.

8. A distributed file sharing device capable of shielding different technology selections, characterized in that: include: The reading unit is used to read the configuration file of the business service to obtain the specific shared storage selection; Initialization unit, used to uniformly initialize the common interfaces of different shared storage options; A creation unit is used to create a connection pool for distributed shared storage for shared storage selection with a storage network protocol; A construction unit for building a unified universal access interface using the facade mode; The sharing unit is used for business services to complete file sharing based on the universal access interface and the connection pool.

9. A computer-readable storage medium, characterized in that The storage medium stores computer instructions, which, when executed on a computer, enable the computer to execute the method according to any one of claims 1 to 7.

10. An electronic device, characterized in that: include: memory and processor; The memory is used to store computer instructions; The processor is configured to call the computer instructions stored in the memory so that the electronic device executes the method according to any one of claims 1 to 7.

Images