Configuration plug-in implementation method based on Extism framework

Abstract

The invention discloses a plug-in configuration implementation method based on an Extim framework, which is characterized in that configuration information is independent from a traditional external configuration center or a configuration file by using a Wasm plug-in, a complex configuration center system does not need to be additionally deployed, the resource overhead of the system is reduced, hot update of configuration is realized by packaging configuration parameters in the Wasm plug-in, and the configuration efficiency is improved. The application can detect and load the new-version plug-in and a naming and recording mechanism for the plug-in version without restarting in the running process, plug-in version management under the multi-pod environment is achieved, it is ensured that the plug-in of the same version is used in each pod, dynamic adjustment and flexible calling of configuration parameters are achieved through an interface provided by an Extism framework, and therefore the configuration efficiency is improved. The application can read and modify the configuration parameters at any time according to the service requirements, so that the configuration can be quickly customized in a changeable service environment, and the self-adaptive requirements of various service logics in a complex scene are met.

Description

Technical Field

[0001] The present application relates to the field of software engineering technology, and in particular to a configuration plug-in implementation method based on the Extism framework. Background Art

[0002] With the continuous development of software systems, configuration management has become an important means to achieve system customization and business logic control. Currently, many software applications manage the execution process of business logic through configuration parameters, supporting the implementation of multiple business scenarios based on different configurations on the basis of the same code. However, in the existing technology, configuration management and update have the following problems:

[0003] Limitations of configuration methods: Traditional configuration management mostly uses configuration files or configuration centers. Configuration files are usually loaded when the service starts. If the configuration parameters need to be updated, the new configuration usually needs to be restarted for the service to take effect. This process will interrupt the normal operation of the service and affect business continuity. In addition, although the deployment of a configuration center alone can achieve real-time updates, it has high requirements for system resources and usually requires the maintenance of additional configuration services, which increases the complexity of the system and operation and maintenance costs.

[0004] Lack of lightweight and flexibility: Current configuration management solutions mostly rely on external configuration centers or databases, which causes the system to rely on more external components when updating configurations. These components usually require specialized operation and maintenance personnel to maintain them, increasing the complexity of development and operation and maintenance. At the same time, configuration centers often have high requirements for performance and storage, making it difficult to achieve lightweight configuration management.

[0005] Configuration consistency in distributed systems: In a multi-pod environment or distributed system, different nodes need to maintain the same configuration version to ensure the correct operation of the system. Existing solutions usually rely on databases or cache layers to synchronize and manage configuration versions, but this process lacks real-time and automation, and is prone to configuration asynchrony, which in turn leads to inconsistent business logic.

[0006] Therefore, the existing configuration management methods face problems such as low efficiency, high resource usage, difficult maintenance, and difficulty in ensuring configuration consistency. Summary of the invention

[0007] The present application provides a configuration plug-in implementation method based on the Extism framework, aiming to solve the problems faced by the existing configuration management methods such as low efficiency, high resource usage, high maintenance difficulty, and difficulty in ensuring configuration consistency.

[0008] The present application provides a configuration plug-in implementation method based on the Extism framework, the method comprising:

[0009] Writing Wasm plug-in code based on the Extism framework, wherein the plug-in includes a global data structure for storing configuration information, wherein the configuration information includes system default configuration parameters and corresponding values ​​of the configuration parameters;

[0010] Write a method to call the Wasm plug-in in the target application, request the plug-in by passing in the parameter name, and obtain the corresponding configuration information value; design the interface in the target application to support the upload and download functions of the plug-in, so that the plug-in file is persistently stored on the object storage server and supports containerized deployment;

[0011] The plug-in naming format is set to "[plug-in name]-version number.wasm" to identify and manage plug-in versions; the plug-in version information used by the current application is recorded through a database or cache to keep the plug-in version consistent in a multi-pod environment;

[0012] When the configuration information needs to be updated during the operation of the target application, the plug-in code is modified and compiled to generate a new plug-in version, which is uploaded to the application pod through the interface; the target application detects whether the plug-in version is consistent each time the plug-in is called. If a new version is detected, the old version is downloaded and replaced to achieve real-time update of configuration parameters.

[0013] In the above solution, optionally, the plug-in supports dynamic update of configuration information stored in a global data structure, and the data structure can be read and modified at any time during the operation of the application.

[0014] In the above solution, optionally, the method designs a naming format of "[plugin name]-version number.wasm" so that each compiled plug-in version has a unique identifier, so as to quickly identify the version number when managing multiple versions.

[0015] In the above solution, optionally, the application interacts with the plug-in through an interface, and the interface supports upload, download, deletion, version switching and parameter calling operations of the plug-in.

[0016] In the above solution, optionally, the method provides a consistency check mechanism in a multi-pod environment by recording the version information of the current plug-in in the persistence layer, so as to ensure that the plug-in version in each pod is consistent.

[0017] In the above solution, optionally, the method includes real-time detection and update of the plug-in version during application operation, so as to ensure that the configuration parameters can take effect immediately when the business logic is changed.

[0018] In the above solution, optionally, the hot update process of the plug-in includes a locking mechanism to lock the global variables and the persistent data layer when the plug-in is updated.

[0019] In the above solution, optionally, the plug-in uploads the new version of the plug-in to the application pod through an interface in a containerized deployment environment, and points the plug-in path to the latest plug-in version.

[0020] In the above solution, optionally, the method includes a plug-in version rollback mechanism, and when a compatibility problem or failure is detected in a new plug-in version, the application automatically rolls back the plug-in to the last stable version.

[0021] In the above solution, optionally, the method locally stores the configuration information of the plug-in through a cache mechanism, and ensures the real-time nature of the data by periodically refreshing the cache content.

[0022] Compared with the prior art, this application has at least the following beneficial effects:

[0023] Based on further analysis and research of existing technical problems, this application recognizes that existing configuration management methods face problems such as low efficiency, high resource usage, high maintenance difficulty, and difficulty in ensuring configuration consistency. Through the use of Wasm plug-ins, this application separates configuration information from traditional external configuration centers or configuration files, without the need to deploy complex configuration center systems, reducing system resource overhead, simplifying the configuration management process, and reducing dependence on professional operation and maintenance personnel, which is suitable for lightweight application scenarios. This application implements hot updates of configurations by encapsulating configuration parameters in Wasm plug-ins. Applications can detect and load new versions of plug-ins without restarting during operation, so that new configurations take effect in real time, ensuring the continuity of business logic and solving the problem of traditional configuration file updates relying on service restarts. Through the naming and recording mechanism of plug-in versions, this application implements plug-in version management in a multi-pod environment, ensuring that the same version of the plug-in is used in each pod, thereby effectively avoiding the problem of inconsistent business logic caused by asynchronous configuration in distributed systems. This application uses the interface provided by the Extism framework to implement dynamic adjustment and flexible calling of configuration parameters. The application can read and modify configuration parameters at any time according to business needs, which facilitates rapid customization of configuration in a changing business environment and meets the adaptive needs of various business logics in complex scenarios.

[0024] This application provides a method for hot-updating configuration parameters of a lightweight Wasm plug-in based on the Extism framework, thereby changing the operation of business logic at any time. It can flexibly control the switching of functions and runtime parameters according to needs, facilitate management and quickly customize business processes, and optimize the current software development problems such as the need to restart services to modify configurations and the heavy burden of separately deploying configuration centers. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1A flowchart of a configuration plug-in implementation method based on the Extism framework provided in one embodiment of the present application;

[0026] Figure 2 An architecture diagram of a configuration plug-in implementation method based on the Extism framework provided in one embodiment of the present application;

[0027] Figure 3 A schematic diagram of the hot update process of controlling a plug-in according to a configuration plug-in implementation method based on the Extism framework provided in one embodiment of the present application. DETAILED DESCRIPTION

[0028] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0029] In one embodiment, Figure 1 As shown, a configuration plug-in implementation method based on the Extism framework is provided, including the following steps:

[0030] Writing Wasm plug-in code based on the Extism framework, wherein the plug-in includes a global data structure for storing configuration information, wherein the configuration information includes system default configuration parameters and corresponding values ​​of the configuration parameters;

[0031] Write a method to call the Wasm plug-in in the target application, request the plug-in by passing in the parameter name, and obtain the corresponding configuration information value; design the interface in the target application to support the upload and download functions of the plug-in, so that the plug-in file is persistently stored on the object storage server and supports containerized deployment;

[0032] The plug-in naming format is set to "[plug-in name]-version number.wasm" to identify and manage plug-in versions; the plug-in version information used by the current application is recorded through a database or cache to keep the plug-in version consistent in a multi-pod environment;

[0033] When the configuration information needs to be updated during the operation of the target application, the plug-in code is modified and compiled to generate a new plug-in version, which is uploaded to the application pod through the interface; the target application detects whether the plug-in version is consistent each time the plug-in is called. If a new version is detected, the old version is downloaded and replaced to achieve real-time update of configuration parameters.

[0034] This embodiment proposes a configuration plug-in implementation method based on the Extism framework, which manages configuration parameters through a WebAssembly (Wasm) plug-in, implements lightweight, flexible, and real-time update-supported configuration management, and has the following technical effects:

[0035] Realize lightweight and independent configuration management: This embodiment uses the Wasm plug-in to separate the configuration information from the traditional external configuration center or configuration file. There is no need to deploy a complex configuration center system, which reduces the system's resource overhead, simplifies the configuration management process, and reduces dependence on professional operation and maintenance personnel. It is suitable for lightweight application scenarios.

[0036] Support real-time update of configuration parameters: By encapsulating the configuration parameters in the Wasm plug-in, this application realizes hot update of the configuration. The application can detect and load the new version of the plug-in without restarting during operation, so that the new configuration takes effect in real time, ensuring the continuity of business logic and solving the problem that traditional configuration file updates depend on service restart.

[0037] Ensure configuration consistency in a multi-pod environment: Through the naming and recording mechanism of the plug-in version, this application implements plug-in version management in a multi-pod environment, ensuring that the same version of the plug-in is used in each pod, thereby effectively avoiding the problem of inconsistent business logic caused by asynchronous configuration in the distributed system.

[0038] Improve the flexibility of configuration management: This application uses the interface provided by the Extism framework to implement dynamic adjustment and flexible calling of configuration parameters. The application can read and modify configuration parameters at any time according to business needs, which facilitates rapid customization of configuration in a changing business environment and meets the adaptive needs of various business logics in complex scenarios.

[0039] This embodiment can effectively solve the problems of limitations, real-time performance, lightweight, and distributed consistency of the configuration management method mentioned in the background technology, and provide a more efficient and reliable configuration management solution for applications.

[0040] In this embodiment, the plug-in supports dynamic updating of configuration information stored in a global data structure, and the data structure can be read and modified at any time during the operation of the application.

[0041] This embodiment provides an implementation method for dynamically storing and managing configuration information in an application through a global data structure. This implementation method brings significant technical effects, especially in terms of enhancing system flexibility, real-time performance and adaptability.

[0042] First, the dynamic storage and management method enables configuration parameters to be read and modified at any time during application operation, thereby realizing a true "hot update" function. Traditional configuration management solutions usually rely on external configuration files or databases to manage configuration parameters. Once these parameters are set, it is difficult to dynamically adjust them during system operation, especially static configuration files that require restarting the service to take effect. The solution proposed in this embodiment stores configuration parameters through a global data structure, and can directly read and operate configuration items at the application level, thereby avoiding the need to restart the service. This real-time dynamic adjustment mechanism is particularly important for application scenarios that require frequent changes to parameter settings. For example, in high-concurrency businesses, the system can adjust parameters in real time to optimize performance or change business logic to adapt to changing business needs.

[0043] In addition, dynamically storing configuration information through a global data structure can significantly improve the flexibility of the system. Since all configuration parameters are centrally stored in a global data structure, the system can call and access the configuration information in the data structure at any time without relying on external configuration center services or performing additional I / O operations. This design not only ensures the speed of configuration calls, but also simplifies the system architecture, making the application no longer dependent on complex external components. Especially in a distributed system environment, the global data structure makes the system configuration calls between different nodes more consistent and synchronized, which helps to ensure configuration consistency in a multi-node environment.

[0044] Through this design, the technical solution of this embodiment can also achieve performance optimization. In traditional configuration solutions, external configuration files or database access may bring a large I / O burden, while the configuration information dynamically stored in the application memory can significantly reduce the number of external accesses, reduce latency, and improve the response speed of the system. In addition, the dynamic management method also facilitates fast switching under different business needs, and is particularly suitable for systems that require frequent configuration adjustments, such as large-scale distributed applications.

[0045] The solution for dynamically storing and managing configuration information in a global data structure provided in this embodiment has important technical effects in terms of flexibility, real-time performance, architecture simplification, and performance optimization, and meets the requirements for efficient and convenient system configuration management under modern complex business needs.

[0046] In this embodiment, the method designs a naming format of "[plugin name]-version number.wasm" so that each compiled plug-in version has a unique identifier, so as to quickly identify the version number when managing multiple versions.

[0047] This embodiment proposes a mechanism for identifying and managing plugin files through a specific naming format "[plugin name]-version number.wasm" to achieve unique identification and accurate calling of plugin versions. This naming and management method brings significant technical effects, especially in ensuring system stability, version consistency and configuration file management convenience.

[0048] First, use the naming mechanism of "[plugin name]-version number.wasm" format to make each plug-in version file have a unique identifier, which can effectively avoid the confusion of traditional configuration files or plug-ins in version management. In traditional configuration management solutions, there are usually confusion problems caused by version updates or overwriting, and it is difficult to clearly identify the version of the file. Through a unified naming format, the version number of the plug-in can be directly identified during the plug-in update process without additional records or searches, which greatly simplifies the version management process and can effectively prevent incorrect calls caused by version confusion.

[0049] Secondly, this naming format provides better support for multi-version management, allowing the system to quickly switch between different versions, facilitating historical version backtracking or debugging. When the system needs to roll back or check the plug-in version, it can directly identify and locate the corresponding plug-in file by version number, without the need to compare or verify in multiple files. This naming mechanism can provide important guarantees for the reliability of the system, especially in complex application environments, and can significantly improve the flexibility of the system for version control.

[0050] In addition, this naming mechanism facilitates consistent management in a multi-pod environment. In a multi-pod environment, each node may have a different plug-in version. In this case, unified identification with version numbers can ensure that the plug-in version referenced by each pod node remains consistent, reducing business logic errors caused by inconsistent plug-in versions. The solution of using a naming format to identify plug-ins also simplifies plug-in update management in a multi-pod environment. During the update process, the plug-in version of each pod node can be detected and compared based on the version number alone, greatly improving the efficiency of consistency management.

[0051] Finally, the unified naming format also facilitates the storage, management and archiving of plug-in files. The version number can easily realize the classification, storage and management of plug-ins of different versions, which is convenient for subsequent query and tracing. In addition, when the plug-in is archived, the corresponding directory structure can also be automatically generated according to the naming format, which improves the orderliness of storage and the convenience of management.

[0052] In this embodiment, the application interacts with the plug-in through an interface, and the interface supports upload, download, deletion, version switching, and parameter call operations of the plug-in.

[0053] This embodiment proposes to interact with the plug-in through the application interface, and supports operations such as plug-in upload, download, delete, version switch and parameter call. This solution brings significant technical effects, especially in improving the flexibility of system configuration management, simplifying the operation process, and supporting complex application scenarios.

[0054] First, plug-in management is implemented through interfaces, so that the system can flexibly manage plug-ins without restarting services. In traditional configuration management solutions, it is usually necessary to manually operate files or use configuration centers for management, which is not only inefficient, but may also require restarting services for new configurations to take effect. By managing plug-ins through interfaces, applications can upload new plug-ins or switch plug-in versions at any time during runtime, giving the system greater runtime flexibility and the ability to adapt to frequent changes in business needs.

[0055] Secondly, the interface supports upload, download, and delete operations, which can significantly simplify the system configuration update process. Users or developers can upload and switch versions of plug-ins through the interface without manually intervening in file storage or version records. This greatly simplifies the configuration operation steps and improves management efficiency, which is especially suitable for application in distributed systems or microservice architectures. At the same time, the download and delete functions provide a convenient means for managing redundant or old plug-ins in the application, which helps maintain the neatness and accuracy of the plug-in library.

[0056] In addition, the version switching function supported by the interface can easily implement the rollback and adjustment of the plug-in version in the application, improving the system's ability to respond quickly to different business needs and scenarios. When the business scenario changes, the system can quickly switch to the applicable plug-in version through the interface without restarting the service or significantly changing the configuration. This has significant advantages in high-concurrency scenarios or applications that require frequent parameter adjustments. With the version switching function, the system can more easily trace back to historical versions for error diagnosis or reproduction of historical business logic.

[0057] Finally, the interface also supports the call of configuration parameters in the plug-in, realizing centralized control of configuration management. The design of the interface enables the application layer to access and control configuration items in a more convenient way, avoiding scattered file operations or complex calling processes. This centralized management method improves the convenience and maintainability of system operation, while reducing the risk of errors caused by manual operation.

[0058] The plug-in management solution implemented by the interface in this embodiment has important technical effects in terms of flexibility, convenience, real-time and centralized control, and provides an easy-to-operate, efficient and convenient configuration management method for the system.

[0059] In this embodiment, the method provides a consistency check mechanism in a multi-pod environment by recording the version information of the current plug-in in the persistence layer, so as to ensure that the plug-in version in each pod is consistent.

[0060] In this embodiment, the method includes real-time detection and updating of the plug-in version during application operation, so as to ensure that the configuration parameters can take effect immediately when the business logic is changed.

[0061] In this embodiment, the hot update process of the plug-in includes a locking mechanism, which locks the global variables and the persistent data layer when the plug-in is updated.

[0062] In this embodiment, the plug-in uploads the new version of the plug-in to the application pod through an interface in a containerized deployment environment, and points the plug-in path to the latest plug-in version.

[0063] In this embodiment, the method includes a plug-in version rollback mechanism. When a compatibility problem or failure is detected in a new plug-in version, the application automatically rolls back the plug-in to the last stable version.

[0064] In this embodiment, the method locally stores the configuration information of the plug-in through a cache mechanism, and ensures the real-time nature of the data by periodically refreshing the cache content.

[0065] In one embodiment, Figure 2 As shown, an architectural diagram of the technical solution of this embodiment is provided, and the following are the detailed implementation steps proposed in this embodiment.

[0066] Written based on Extism's Wasm plugin:

[0067] Extism is a lightweight framework built with WebAssembly (Wasm). It supports running Wasm code on the server, and compiled Wasm plugins can be run in applications.

[0068] Establish an Extism plugin code repository. The repository uses a global data structure to maintain a configuration information, which stores the names and values ​​of various configuration parameters required by the system in the default state, one by one. In addition, the repository has methods for reading the data structure and returning the corresponding values, which are provided for application calls. After all of the above are completed, compile the source code into a wasm type file.

[0069] Application and plugin interaction:

[0070] Write a method to call the Wasm plug-in in the application, for example, take a parameter name as an input parameter, request the plug-in method, and get the value of the parameter. Design an interface for uploading and downloading plug-ins in the application. The plug-in can be uploaded and downloaded to the pod through the interface, and the uploaded plug-in is persisted on the object storage server. When using containerized deployment, upload the compiled plug-in to the same pod of the application through the interface, and the plug-in can be read by specifying the plug-in path. When the plug-in is instantiated successfully, the Wasm plug-in method can be called to read the configuration parameters in the plug-in during application operation, so as to achieve the purpose of flexible control of business logic.

[0071] Version control for plugins:

[0072] The plugin name is designed as [plugin name]-version number.wasm. The advantage of this is that the version number of the compiled plugin can be easily observed, and the version number can be obtained by parsing the plugin file in the application.

[0073] In actual use scenarios, the same application may have multiple pods, so the problem of plugins being out of sync in multiple pods should be avoided. A database / cache combination is used to persistently store the name and version information of the current application Wasm plugin. At the same time, a global variable is maintained in the application, which also stores the plugin name and version information in the current pod. By default, the version in the application is consistent with the plugin version stored in the persistence layer. When the plugin version is updated, the version of the persistence layer will change. At this time, you only need to update the plugin version in the current pod by downloading the new plugin and deleting the original plugin.

[0074] Hot update of plugins:

[0075] When the configuration parameters in the plug-in need to be modified during the running of the application, it is necessary to modify the configuration information in the plug-in code repository, compile a new Wasm type plug-in, name it with a new version number, and then upload it to the application's pod.

[0076] In order to control the hot update of plug-ins so that the application configuration can be changed in real time, a solution is proposed, such as Figure 3 As shown. In each method of reading configuration parameters, the function of judging the plug-in version is introduced, and the global variable version in the process is compared with the persistence layer. If there is a difference, the version of the persistence layer shall prevail, the new version plug-in is downloaded, and then the configuration items in the new plug-in are read. In addition, there are post-processes such as updating the global variables in the process and removing the old version plug-in. In order to improve performance, the local plug-in version is compared with the cached content, and the process of updating the plug-in version is locked to consider data consistency.

[0077] The key point of this embodiment is to centralize the configuration information of the application into the Wasm plug-in, and embed it into the execution process of the application as a piece of code. When the configuration needs to be updated, it is only necessary to compile the modified content into a new version of the plug-in and upload it to the application pod, thereby realizing hot update of the application configuration.

[0078] This embodiment proposes a solution that can manage the consistency of plug-in versions in multiple pods in a distributed system, so that the same version of the plug-in can always run in multiple pods, effectively avoiding the problem of data inconsistency.

[0079] This embodiment achieves the effect of separating runtime parameters from applications by making application configuration plug-ins, while also avoiding the previous problems of requiring service restarts or the heavy burden of deploying a configuration center separately. In terms of the timeliness of configuration updates, the configuration parameters are made effective in real time and data consistency is achieved through features such as hot updates uploaded by Wasm plug-ins and version consistency control. At the same time, the application is no longer strongly dependent on the configuration center, allowing it to move forward lightly and flexibly respond to different demand process controls.

[0080] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

Claims

1. A configuration plug-in implementation method based on the Extism framework, characterized in that: The method comprises: Writing Wasm plug-in code based on the Extism framework, wherein the plug-in includes a global data structure for storing configuration information, wherein the configuration information includes system default configuration parameters and corresponding values ​​of the configuration parameters; Write a method to call the Wasm plug-in in the target application, request the plug-in by passing in the parameter name, and obtain the corresponding configuration information value; design the interface in the target application to support the upload and download functions of the plug-in, so that the plug-in file is persistently stored on the object storage server and supports containerized deployment; The plug-in naming format is set to "[plug-in name]-version number.wasm" to identify and manage plug-in versions; the plug-in version information used by the current application is recorded through a database or cache to keep the plug-in version consistent in a multi-pod environment; When the configuration information needs to be updated during the operation of the target application, the plug-in code is modified and compiled to generate a new plug-in version, which is uploaded to the application pod through the interface; the target application detects whether the plug-in version is consistent each time the plug-in is called. If a new version is detected, the old version is downloaded and replaced to achieve real-time update of configuration parameters.

2. According to the Extism framework-based configuration plug-in implementation method of claim 1, it is characterized in that: The plug-in supports dynamic updating of configuration information stored through a global data structure, which can be read and modified at any time during the operation of the application.

3. The configuration plug-in implementation method based on the Extism framework according to claim 1 is characterized in that: The method designs a naming format "[plugin name]-version number.wasm" so that each compiled plug-in version has a unique identifier, so that the version number can be quickly identified when multiple versions are managed.

4. The configuration plug-in implementation method based on the Extism framework according to claim 1 is characterized in that: The application interacts with the plug-in through an interface, and the interface supports plug-in upload, download, deletion, version switching and parameter calling operations.

5. The configuration plug-in implementation method based on the Extism framework according to claim 1 is characterized in that: The method records the version information of the current plug-in in the persistence layer, and provides a consistency check mechanism in a multi-pod environment to ensure that the plug-in version in each pod is consistent.

6. The configuration plug-in implementation method based on the Extism framework according to claim 1 is characterized in that: The method includes real-time detection and updating of the plug-in version during application operation, so as to ensure that the configuration parameters can take effect immediately when the business logic is changed.

7. The configuration plug-in implementation method based on the Extism framework according to claim 1 is characterized in that: The hot update process of the plug-in includes a locking mechanism to lock the global variables and the persistent data layer when the plug-in is updated.

8. The configuration plug-in implementation method based on the Extism framework according to claim 1 is characterized in that: In a containerized deployment environment, the plug-in uploads a new version of the plug-in to the application pod through an interface, and points the plug-in path to the latest plug-in version.

9. The configuration plug-in implementation method based on the Extism framework according to claim 1 is characterized in that: The method includes a plug-in version rollback mechanism. When a compatibility problem or failure is detected in a new plug-in version, the application automatically rolls back the plug-in to the last stable version.

10. The configuration plug-in implementation method based on the Extism framework according to claim 1 is characterized in that: The method locally stores the configuration information of the plug-in through a cache mechanism, and ensures the real-time nature of the data by periodically refreshing the cache content.

Images