Service plug-in management method and system, electronic equipment and storage medium
By building independent container instances for each business plug-in and managing it, the problem of heavy workload of business plug-in development and integration is solved, reducing the duplicate development part, improving development efficiency and avoiding dependency environment conflicts.
Patent Information
- Application Number
- CN202510186619.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-02-19
- Publication Date
- 2025-06-27
AI Technical Summary
In the prior art, business plug-in development and integration workloads are large, there is a part of repeated development management functions, and there may be conflicts between business plug-ins that depend on the environment.
By building the container instance corresponding to each business plug-in, copy the binary program of the business plug-in to the container instance according to its dependency environment template, storage size requirements and process number requirements configuration information, and copy the binary program of the business plug-in to the container instance, and manage each container instance independently.
It realizes an independent operating environment for each business plug-in, avoids the impact between plug-ins and between plug-ins and ROM systems, reduces the workload of repeated development management functions, and improves development efficiency.
Smart Images

Figure CN120216049A_ABST
Abstract
Description
Background Art
[0002] Currently, each business plugin needs to be developed and adapted separately. All business plugins run together in the ROM system environment. However, the development and integration workload of business plugins is large, and there are duplicate development parts in each business plugin. The duplicate development parts specifically refer to the development parts of management functions, which are time-consuming and laborious. Moreover, there may be conflicts in the dependent environments between business plugins. Summary of the Invention
[0003] The technical problem to be solved by the present invention is to provide a business plugin management method, system, electronic device and storage medium in view of the deficiencies of the prior art, specifically as follows:
[0004] 1) In the first aspect, the present invention provides a business plugin management method, and the specific technical solution is as follows:
[0005] According to the configuration information of the dependent environment template, storage size requirement and process number requirement of each business plugin, a container instance corresponding to each business plugin is constructed;
[0006] The binary programs in each business plugin are respectively copied into the corresponding container instances, and each container instance is managed, wherein the running environments of all container instances are independent of each other.
[0007] The beneficial effects of a business plugin management method provided by the present invention are as follows:
[0008] Each business plugin is respectively encapsulated in different container instances, and the running environments of all container instances are independent of each other, avoiding the influence between business plugins and between business plugins and the ROM system. Moreover, by uniformly managing all container instances, the duplicate development part of "currently each plugin needs to develop a management function separately" can be effectively reduced, and the development efficiency can be improved.
[0009] On the basis of the above solution, a business plugin management method of the present invention can also be improved as follows.
[0010] Further, managing each container instance includes:
[0011] Performing at least one management of deletion, start, stop and query on each container instance.
[0012] Further, it further includes:
[0013] Providing corresponding interfaces for each management of deletion, start, stop and query respectively;
[0014] Performing at least one management of deletion, start, stop and query on each container instance includes:
[0015] Manage at least one of deletion, start, stop, and query for each container instance through multiple provided interfaces.
[0016] Furthermore, it also includes: monitoring and keeping alive each container instance.
[0017] 2) In a second aspect, the present invention also provides a business plugin management system, and the specific technical solution is as follows:
[0018] It includes a container instance construction module and a management module;
[0019] The container instance construction module is used to: construct a container instance corresponding to each business plugin according to the dependency environment template, storage size requirement configuration information, and process number requirement configuration information of each business plugin;
[0020] The management module is used to: copy the binary programs in each business plugin to the corresponding container instances respectively, and manage each container instance, where the running environments of all container instances are independent of each other.
[0021] Based on the above solution, a business plugin management system of the present invention can also be improved as follows.
[0022] Furthermore, the management module is specifically used to: manage at least one of deletion, start, stop, and query for each container instance.
[0023] Furthermore, it also includes an interface providing module, and the interface providing module is used to: provide corresponding interfaces for each management of deletion, start, stop, and query respectively;
[0024] The management module is also specifically used to: manage at least one of deletion, start, stop, and query for each container instance through multiple provided interfaces.
[0025] Furthermore, the management module is also used to: monitor and keep alive each container instance.
[0026] 3) In a third aspect, the present invention also provides an electronic device, which includes a processor. The processor is coupled to a memory, and at least one computer program is stored in the memory. The at least one computer program is loaded and executed by the processor so that the electronic device implements any one of the above business plugin management methods.
[0027] 4) In a fourth aspect, the present invention also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements any one of the above business plugin management methods.
[0028] It should be noted that for the technical solutions of the second to fourth aspects of the present invention and the corresponding possible implementation manners, and the beneficial effects achieved thereby, reference may be made to the above technical effects of the first aspect and its corresponding possible implementation manners, which will not be elaborated herein. BRIEF DESCRIPTION OF THE DRAWINGS
[0029] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the accompanying drawings required for the description of the embodiments of the present invention:
[0030] Figure 1 It is a schematic flowchart of a service plugin management method according to an embodiment of the present invention;
[0031] Figure 2 It is a schematic structural diagram of a service plugin management system according to an embodiment of the present invention;
[0032] Figure 3 It is a schematic structural diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0033] The following describes the principles and features of the present invention. The examples given are only for explaining the present invention and are not intended to limit the scope of the present invention.
[0034] The following uses specific embodiments to elaborate in detail on the technical solutions of the present invention and how the technical solutions of the present invention solve the above technical problems. These several specific embodiments can be combined with each other. For the same or similar concepts or processes, they may not be repeated in some embodiments. The embodiments of the present invention will be described below with reference to the accompanying drawings.
[0035] As Figure 1 shown, a service plugin management method according to an embodiment of the present invention includes the following steps:
[0036] S1. According to the dependency environment template, storage size requirement configuration information, and process number requirement configuration information of each service plugin, construct a container instance corresponding to each service plugin. The specific implementation process is as follows:
[0037] S10. Create a container (such as Docker, Lxc, etc.) file corresponding to the service plugin according to the dependency environment template, storage size requirement configuration information, and process number requirement configuration information of the service plugin;
[0038] S11. Construct a container (such as Docker, Lxc, etc.) image according to the container (such as Docker, Lxc, etc.) file, and obtain a container instance from the container (such as Docker, Lxc, etc.) image. The container instance is a running instance of the container (such as Docker, Lxc, etc.) image.
[0039] Among them, the business plugin is a module that implements corresponding business functions, including but not limited to the following business plugins:
[0040] 1) Data analysis plugin: It can create reports, charts, etc., and can perform operations such as data pivoting, facilitating users to better understand and analyze business data, and also facilitating users to make accurate decisions subsequently.
[0041] 2) Security protection plugin: Specifically includes functions such as firewalls, vulnerability scanning, and encryption, protecting the business system from malicious attacks and data leakage.
[0042] 3) Workflow plugin: It can realize the automated processing of work processes, specifically including functions such as approval processes and task allocation, improving work efficiency.
[0043] 4) Customer relationship management plugin: Includes functions such as customer information management, sales follow-up, and customer reports, and can help users better manage customer relationships.
[0044] 5) Human resource management plugin: Includes functions such as recruitment management, employee attendance, and performance appraisal, and can improve the efficiency of human resource management.
[0045] 6) Permission management plugin: Includes functions such as user role setting and operation log recording, facilitating users to better manage permissions.
[0046] 7) Function extension plugin: Includes payment interface plugins, logistics interface plugins, etc., and can realize functions such as online payment and express query.
[0047] Among them, the dependency environment template of the business plugin refers to a set of dependencies and configuration information necessary to ensure that the business plugin can run normally in a specific environment. The dependency environment template contains detailed information such as software, libraries, frameworks, operating system versions, and hardware configurations required for the operation of the business plugin.
[0048] Among them, the process of obtaining the dependency environment template of the business plugin is as follows:
[0049] S101. Determine the functions of the business plugin, determine the resource requirements and dependencies during the operation of the business plugin, and according to the usage scenario of the business plugin, determine the type of the target environment (such as operating system or hardware platform, etc.), and consider the compatibility between different target environments.
[0050] S102. Obtain all components required for the operation of the business plugin, including operating systems, runtime environments (such as Java, Python, etc.), databases, and middleware, etc.
[0051] S103. Add conditional logic to the preset dependency environment template and configure the dependency information obtained in S101 and S102 (resource requirements, dependencies, types of target environments, all components, library files, configuration files, etc. required for the business plugin during operation), thereby obtaining the dependency environment template for the business plugin. Moreover, during the configuration process, different dependencies and configuration options can also be provided according to the differences in the target environment to improve the flexibility of configuration.
[0052] Among them, the conditional logic of the business plugin refers to: during the design and implementation of the business plugin, according to factors such as the target environment, the logic for the business plugin to implement corresponding functions, such as configuration option management, dependency management, compatibility management, and trigger conditions.
[0053] Among them, the preset dependency environment template is: a template set by the user in advance, or it can also be an existing template currently.
[0054] Optionally, a variable substitution mechanism can also be used to allow users to adjust dependencies and configuration information according to actual needs when applying the dependency environment template of the business plugin.
[0055] Optionally, before S103, it also includes:
[0056] Layer the dependency information obtained in S101 and S102 (resource requirements, dependencies, types of target environments, all components, library files, and configuration files, etc. required for the business plugin during operation) according to the operating system, target environment, components, etc., and then encapsulate different layers into different sets. In S103, when configuring the dependency information obtained in S101 and S102, it can be called from the corresponding sets, which is not easy to cause confusion. Moreover, encapsulating into different sets is more convenient for subsequent maintenance.
[0057] Among them, the process of obtaining the configuration information for the storage size requirement and the process number requirement of the business plugin includes:
[0058] Identify the library files required by the business plugin. The library files include dynamic link libraries (DLLs) and shared object files (SOs), etc., and ensure that the library files are compatible with the target environment. Also, obtain the configuration files required by the business plugin. The configuration files include environment variable settings, system property configurations, configuration information for storage size requirements (including the size of persistent storage, read / write performance requirements, etc.) and configuration information for process number requirements (including whether multiple processes need to run and the communication methods between these processes), etc.
[0059] S2. Copy the binary programs in each business plugin to the corresponding container instances respectively and manage each container instance. Among them, the running environments of all container instances are independent of each other.
[0060] Among them, the binary program in the service plug-in refers to: a computer program that exists in binary form and is relied on or used by the service plug-in. The usage methods of the binary program in the service plug-in are: embedding method, dynamic linking method, and independent execution method.
[0061] Optionally, in the above technical solution, managing each container instance includes:
[0062] Performing at least one of deletion, start, stop, and query management on each container instance.
[0063] Optionally, in the above technical solution, it further includes:
[0064] Providing corresponding interfaces for each of the deletion, start, stop, and query management;
[0065] Performing at least one of deletion, start, stop, and query management on each container instance includes:
[0066] Performing at least one of deletion, start, stop, and query management on each container instance through the provided multiple interfaces. Specifically:
[0067] 1) The interface set for deletion management is called: deletion interface. Through the deletion interface, the resources applied for creating the container instance, such as CPU, memory, disk space, etc., can be released, and the running of the container instance can be stopped. That is to say, the service plug-in corresponding to the container instance is stopped.
[0068] 2) The interface set for start management is called: start interface. Through the start interface, the container instance can be started, that is, the service plug-in corresponding to the container instance is started.
[0069] 3) The interface set for stop management is called: stop interface. Through the stop interface, the running of the container instance can be stopped, that is, the service plug-in corresponding to the container instance is stopped.
[0070] 4) The interface provided for query management is called: query interface. Through the query interface, the running status of the container instance can be queried.
[0071] Among them, some existing software can be used to batch manage multiple container instances, such as Docker Compose, Docker Swarm, or Kubernetes, etc. Also, container instances can be batch created, run, and managed by writing scripts. Through control structures such as loops and conditional judgments, batch operations on multiple container instances can be achieved.
[0072] Optionally, in the above technical solution, it further includes: monitoring and keeping alive each container instance.
[0073] Among them, the process of monitoring container instances includes:
[0074] ① Determine multiple metrics to be monitored, such as CPU usage, memory occupancy, disk I / O, and network traffic, etc., and set the container instances to be monitored, the collection frequency of the metrics to be monitored, and the alarm conditions, etc.
[0075] ② Through a monitoring proxy service (such as the Exporter of Prometheus), collect data of multiple metrics to be monitored of the container instances to be monitored, and usually store the monitored data in the form of time series, or visually display the monitored data in the form of charts, etc.
[0076] Moreover, when the monitored data triggers the alarm condition, a corresponding warning message is sent so that the user can handle it in time.
[0077] Among them, the alarm condition and the corresponding warning message can be set according to the actual situation. For example, the alarm condition can be: when the CPU usage is greater than 50%, a warning message of "too high CPU usage" is sent.
[0078] Among them, the process of keeping the container instances alive includes:
[0079] ① Set the restart policy of the container instance. The restart policy of the container instance can be: "do not restart when the container instance exits, only restart when the container instance exits with a non-zero status code, the container instance always restarts (unless manually stopped), the container always restarts (unless the container (such as Docker or Lxc, etc.) daemon process itself is stopped manually)", etc. The restart policy of the container instance can be set according to the actual situation.
[0080] ② Keep the container instance alive according to the restart policy of the container instance.
[0081] In the above embodiments, although the steps are numbered S1, S2, etc., they are only specific embodiments given by the present invention. Those skilled in the art can adjust the execution order of S1, S2, etc. according to the actual situation, which is also within the protection scope of the present invention. It can be understood that in some embodiments, it may include some or all of the above embodiments.
[0082] Such as Figure 2 As shown, a service plugin management system 200 according to an embodiment of the present invention includes a container instance construction module 201 and a management module 202;
[0083] The container instance construction module 201 is used to: construct a container instance corresponding to each service plugin according to the dependency environment template, the configuration information of the storage size requirement, and the configuration information of the process number requirement of each service plugin;
[0084] The management module 202 is configured to: copy the binary programs in each service plugin to corresponding container instances respectively, and manage each container instance, wherein the operating environments of all container instances are independent of each other.
[0085] Optionally, in the above technical solution, the management module 202 is specifically configured to: perform at least one of deletion, start, stop, and query management on each container instance.
[0086] Optionally, in the above technical solution, an interface providing module is further included, and the interface providing module is configured to: provide corresponding interfaces for each of the deletion, start, stop, and query management respectively;
[0087] The management module is further specifically configured to: perform at least one of deletion, start, stop, and query management on each container instance through the provided multiple interfaces.
[0088] Optionally, in the above technical solution, the management module is further configured to: monitor and keep alive each container instance.
[0089] It should be noted that the beneficial effects of the service plugin management system 200 provided in the above embodiments are the same as those of the above service plugin management method, and will not be elaborated here. In addition, when the system provided in the above embodiments implements its functions, only the above division of each functional module is used for illustration. In practical applications, the above functions can be allocated to different functional modules according to needs, that is, the system can be divided into different functional modules according to the actual situation to complete all or part of the functions described above. In addition, the system and method embodiments provided in the above embodiments belong to the same inventive concept, and the specific implementation process can be seen in the method embodiments, which will not be elaborated here.
[0090] Among them, the service plugin management system of the present invention can be a computer program (including program code) running in a computer device. For example, the service plugin management system of the present invention is an application software and can be used to execute the corresponding steps in the service plugin management method of the present invention.
[0091] In some embodiments, the service plug-in management system of the present invention can be implemented in a combination of software and hardware. As an example, the service plug-in management system of the present invention can be a processor in the form of a hardware decoding processor, which is programmed to execute the service plug-in management method of the present invention. For example, a processor in the form of a hardware decoding processor can employ one or more application specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs) or other electronic components.
[0092] Among them, the modules involved in the embodiments of the present invention can be implemented in software or in hardware. Among them, the name of the module does not constitute a limitation to the module itself in some cases.
[0093] An electronic device according to an embodiment of the present invention includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the above-mentioned service plug-in management method is implemented. That is to say, an electronic device according to an embodiment of the present invention may include, but is not limited to: a processor and a memory; the memory is used to store a computer program; the processor is used to execute the service plug-in management method shown in any embodiment of the present invention by calling the computer program.
[0094] In an alternative embodiment, an electronic device is provided, as Figure 3 shown, Figure 3 the electronic device 4000 shown includes: a processor 4001 and a memory 4003. Among them, the processor 4001 and the memory 4003 are connected, such as connected through a bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004, and the transceiver 4004 can be used for data interaction between the electronic device and other electronic devices, such as data sending and / or data receiving, etc. It should be noted that in practical applications, the transceiver 4004 is not limited to one, and the structure of the electronic device 4000 does not constitute a limitation to the embodiments of the present invention.
[0095] The processor 4001 can be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of the present invention. The processor 4001 can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.
[0096] The bus 4002 can include a path for transmitting information between the above components. The bus 4002 can be a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus 4002 can be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, Figure 3 only a thick line is used to represent the bus 4002 in the figure, but it does not mean that there is only one bus or one type of bus.
[0097] The memory 4003 can be a ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, a RAM (Random Access Memory) or other type of dynamic storage device that can store information and instructions, or it can also be an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory), or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.
[0098] The memory 4003 is used to store the application program code (computer program) for implementing the solution of the present invention, and is controlled by the processor 4001 for execution. The processor 4001 is used to execute the application program code stored in the memory 4003 to implement the content shown in the foregoing method embodiments.
[0099] Among them, the electronic device may also be a terminal device, and the terminal device may be any device on which an application can be installed, including at least one of a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, a smart TV, and a smart vehicle-mounted device.
[0100] It should be noted that Figure 3 the illustrated electronic device is only an example, and should not impose any limitations on the functions and usage scope of the embodiments of the present invention.
[0101] A computer-readable storage medium according to an embodiment of the present invention has a computer program stored thereon, and when the computer program is executed by a processor, the above-mentioned any business plug-in management method is implemented.
[0102] Optionally, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), a magnetic tape, a floppy disk, and an optical data storage device, etc.
[0103] In an exemplary embodiment, there is also provided a computer program product or a computer program. The computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the electronic device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the electronic device executes the above-mentioned any business plug-in management method.
[0104] Computer program code for performing the operations of the present invention may be written in one or more programming languages or combinations thereof. The above-mentioned programming languages include object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, executed as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or it may be connected to an external computer (e.g., by connecting through the Internet using an Internet service provider).
[0105] It should be understood that the flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code that contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a dedicated hardware-based system for performing the specified functions or operations, or may be implemented by a combination of dedicated hardware and computer instructions.
[0106] The computer-readable storage medium provided by the embodiments of the present invention may be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EEPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
[0107] The above computer-readable storage medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to execute the method shown in the above embodiments.
[0108] The above description is only a preferred embodiment of the present invention and an explanation of the applied technical principles. Those skilled in the art should understand that the scope of disclosure involved in the present invention is not limited to the technical solutions formed by the specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosure concept. For example, the technical solutions formed by mutually replacing the above features with the (but not limited to) technical features with similar functions disclosed in the present invention.
[0109] It should be noted that the terms "first", "second", etc. in the specification and claims of this application are used to distinguish similar objects, and represent a limitation on a specific order or sequence. In appropriate cases, the order of use of similar objects can be interchanged so that the embodiments of this application described here can be implemented in an order other than the illustrated or described order.
[0110] Those skilled in the art know that the present invention can be implemented as a system, a method, or a computer program product. Therefore, the present invention can be specifically implemented in the following forms: it can be completely hardware, can also be completely software (including firmware, resident software, microcode, etc.), or can also be in the form of a combination of hardware and software, which is generally referred to as "circuit", "module" or "system" in this article. In addition, in some embodiments, the present invention can also be implemented in the form of a computer program product in one or more computer-readable media, which contains computer-readable program code.
[0111] Although the embodiments of the present invention have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those of ordinary skill in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present invention.
Claims
1. A service plug-in management method, characterized in that: include: Build a container instance corresponding to each business plug-in based on the dependent environment template of each business plug-in, the configuration information of the storage size requirement, and the configuration information of the process number requirement; The binary program in each business plug-in is copied to the corresponding container instance, and each container instance is managed, wherein the operating environment of all container instances is independent of each other.
2. A service plug-in management method according to claim 1, characterized in that: Manage each container instance, including: Manage at least one of the following operations: delete, start, stop, and query each container instance.
3. A service plug-in management method according to claim 2, characterized in that: Also includes: Provide corresponding interfaces for each management of deletion, start, stop and query; Manage at least one of the following operations for each container instance: delete, start, stop, and query: At least one of deletion, start, stop, and query is managed for each container instance through multiple provided interfaces.
4. A service plug-in management method according to any one of claims 1 to 3, characterized in that: Also includes: Monitor and keep each container instance alive.
5. A business plug-in management system, characterized in that: Includes container instance building modules and management modules; The container instance construction module is used to: construct a container instance corresponding to each business plug-in according to the dependent environment template of each business plug-in, the configuration information of the storage size requirement and the configuration information of the process number requirement; The management module is used to copy the binary program in each service plug-in to the corresponding container instance and manage each container instance, wherein the operating environments of all container instances are independent of each other.
6. A business plug-in management system according to claim 5, characterized in that: The management module is specifically used to manage at least one of deletion, start, stop and query of each container instance.
7. A business plug-in management system according to claim 6, characterized in that: It also includes an interface providing module, which is used to provide a corresponding interface for each management of deletion, start, stop and query; The management module is also specifically used to manage at least one of deletion, start, stop and query of each container instance through multiple interfaces provided.
8. A business plug-in management system according to any one of claims 5 to 7, characterized in that: The management module is also used to monitor and keep each container instance alive.
9. An electronic device, characterized in that: The invention comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements a service plug-in management method as claimed in any one of claims 1 to 4 when executing the computer program.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the service plug-in management method according to any one of claims 1 to 4 is implemented.