Middleware management method and device, storage medium and electronic equipment
By receiving management instructions to generate and detect middleware, and performing full life cycle management operations, the incomplete problem of middleware service management is solved, efficient resource utilization and security improvement is achieved, and it is suitable for cloud-native microservice architecture.
Patent Information
- Application Number
- CN202510529493.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-25
- Publication Date
- 2025-07-25
AI Technical Summary
The existing middleware service management methods lack comprehensive control of the entire life cycle, and it is difficult to adapt to the rapidly changing business needs and technical environment. There are performance bottlenecks and security risks caused by lack of standardized service creation, inefficient start-up and restart, resource leakage caused by incomplete stop and uninstallation, and performance bottlenecks and security risks caused by insufficient monitoring.
It provides a middleware management method, which generates target middleware based on user configuration, detects startup conditions, performs restart, stop and uninstall operations, including dependency checking, resource checking and performance monitoring, builds a full life cycle management architecture, and realizes standardized processes and intelligent monitoring.
It realizes the systematized management of middleware services throughout the life cycle, improves management efficiency, service availability and security, optimizes resource utilization, and is suitable for cloud-native microservice architecture.
Smart Images
Figure CN120371569A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and particularly to a method, apparatus, storage medium, and electronic device for managing middleware. Background Art
[0002] With the rapid development of information technology and the acceleration of enterprise digital transformation, middleware, as a key bridge connecting different systems, platforms, and applications, has become increasingly important. However, in a complex and ever-changing IT environment, the management of middleware services faces many challenges, such as the lack of a standardized process for service creation, low efficiency in startup and restart, resource leakage caused by incomplete stop and uninstall, and performance bottlenecks and security risks caused by insufficient monitoring.
[0003] Most of the existing middleware service management methods focus on the management of a single link, lacking comprehensive control over the entire life cycle, and it is difficult to adapt to the rapidly changing business needs and technical environment. Summary of the Invention
[0004] The technical problem to be solved by this application is to provide a method, apparatus, storage medium, and electronic device for managing middleware, which can effectively manage the entire life cycle of middleware services. The specific solutions are as follows:
[0005] A method for managing middleware, the method includes:
[0006] Receiving a first middleware management instruction;
[0007] In response to the first middleware management instruction, determining a target middleware to be started, the target middleware being generated based on middleware configuration information configured by a user;
[0008] Detecting whether the target middleware meets a preset startup condition;
[0009] When the target middleware meets the preset startup condition, starting the target middleware;
[0010] Receiving a second middleware management instruction;
[0011] In response to the second middleware management instruction, performing a management operation corresponding to the second middleware management instruction on the target middleware, the management operation including one of restarting the middleware service, stopping the middleware service, and uninstalling the middleware service.
[0012] For the above method, optionally, the process of generating the target middleware based on middleware configuration information configured by a user includes:
[0013] Receiving middleware configuration information configured by a user;
[0014] Obtain the corresponding configuration template from a preset template library according to the middleware type and version in the middleware configuration information;
[0015] Run the configuration script to generate the target middleware according to the middleware configuration information and the configuration template, where the configuration script is pre-generated according to middleware characteristics.
[0016] In the above method, optionally, the detecting whether the target middleware meets the preset startup conditions includes:
[0017] Determine each dependency of the target middleware;
[0018] Detect whether each dependency of the target middleware is complete;
[0019] When each dependency of the target middleware is complete, determine that the target middleware meets the preset startup conditions.
[0020] In the above method, optionally, after starting the target middleware, it further includes:
[0021] Monitor the performance parameters and running status corresponding to the target middleware.
[0022] In the above method, optionally, the management operation is an operation to stop the middleware service;
[0023] The performing the management operation corresponding to the second middleware management instruction on the target middleware includes:
[0024] Determine the historical requests currently to be processed by the target middleware, and control the target middleware to stop receiving new requests;
[0025] After detecting that the historical requests received by the target middleware are processed, control the target middleware to stop running.
[0026] In the above method, optionally, the management operation is an operation to restart the middleware service;
[0027] The performing the management operation corresponding to the second middleware management instruction on the target middleware includes:
[0028] Start the target service instance of the target middleware;
[0029] After the target service instance of the target middleware is started, control the historical service instance of the target middleware to stop running to complete the restart of the middleware service.
[0030] In the above method, optionally, the management operation is an operation to uninstall the middleware service;
[0031] Performing the management operation corresponding to the second middleware management instruction on the target middleware includes:
[0032] Uninstalling the target middleware and releasing the resources occupied by the target middleware to complete the uninstallation of the middleware service.
[0033] A middleware management device includes:
[0034] A first receiving unit for receiving a first middleware management instruction;
[0035] A determination unit for determining a target middleware to be started in response to the first middleware management instruction, where the target middleware is generated based on middleware configuration information configured by a user;
[0036] A detection unit for detecting whether the target middleware meets a preset start condition;
[0037] A start unit for starting the target middleware when the target middleware meets the preset start condition;
[0038] A second receiving unit for receiving a second middleware management instruction;
[0039] An execution unit for performing the management operation corresponding to the second middleware management instruction on the target middleware in response to the second middleware management instruction, where the management operation includes one of restarting the middleware service, stopping the middleware service, and uninstalling the middleware service.
[0040] A storage medium includes stored instructions, where when the instructions run, they control a device where the storage medium is located to execute the middleware management method as described above.
[0041] An electronic device includes a memory and one or more instructions, where one or more instructions are stored in the memory and are configured to be executed by one or more processors to execute the middleware management method as described above.
[0042] Based on the middleware management method and system provided by the present application embodiment above, the method includes: receiving a first middleware management instruction; in response to the first middleware management instruction, determining a target middleware to be started, where the target middleware is generated based on middleware configuration information configured by a user; detecting whether the target middleware meets a preset start condition; starting the target middleware when the target middleware meets the preset start condition; receiving a second middleware management instruction; in response to the second middleware management instruction, performing a management operation corresponding to the second middleware management instruction on the target middleware, where the management operation includes one of restarting the middleware service, stopping the middleware service, and uninstalling the middleware service. Applying the method provided by the embodiments of the present application can effectively manage the entire life cycle of the middleware service. BRIEF DESCRIPTION OF THE DRAWINGS
[0043] To more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only the embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained according to the provided drawings without creative efforts.
[0044] Figure 1 It is a flowchart of a method for managing a middleware provided by the present application;
[0045] Figure 2 It is a flowchart of a process for generating a target middleware based on middleware configuration information configured by a user provided by the present application;
[0046] Figure 3 It is a management flowchart of a middleware provided by the present application;
[0047] Figure 4 It is a schematic structural diagram of a middleware management device provided by the present application;
[0048] Figure 5 It is a schematic structural diagram of an electronic device provided by the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0049] The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present application.
[0050] In this application, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or device comprising the element.
[0051] An embodiment of this application provides a method for managing middleware. This method can be applied to an electronic device. The flowchart of this method is as Figure 1 shown and specifically includes:
[0052] S101: Receive a first middleware management instruction.
[0053] Optionally, the first middleware instruction can be a control signal triggered by a user or a system for initializing middleware, including the identifier of the target middleware and configuration requirements.
[0054] In this embodiment, instructions are received through an API interface, a command-line tool or a graphical interface, the parameters in the instructions (such as middleware type, version, resource quota) are parsed, and subsequent processes are triggered.
[0055] S102: In response to the first middleware management instruction, determine the target middleware to be started. The target middleware is generated based on the middleware configuration information configured by the user.
[0056] In this embodiment, the target middleware can be a middleware instance generated according to user configuration, including a runtime environment, dependent libraries, service interfaces, etc.
[0057] In some embodiments, according to the identifier in the first middleware management instruction, matching configuration information is retrieved from the middleware configuration library, and a deployment description file of the middleware instance is generated by calling a configuration template.
[0058] In an embodiment provided by this application, based on the above solution, optionally, the process of generating the target middleware based on the middleware configuration information configured by the user is as Figure 2 shown and includes:
[0059] S201: Receive the middleware configuration information configured by the user.
[0060] In this embodiment, the middleware configuration information can be user-defined middleware instantiation parameters, including middleware type, version number, runtime parameters, etc. The runtime parameters can include memory quota, port number, cluster scale, etc.
[0061] S202: Obtain the corresponding configuration template from a preset template library according to the middleware type and version in the middleware configuration information.
[0062] In this embodiment, the template library stores a set of templates for different middleware types and version types, and the configuration template can be retrieved from the template library based on the middleware type and version in the middleware configuration information.
[0063] S203: Run the configuration script to generate the target middleware according to the middleware configuration information and the configuration template, where the configuration script is pre-generated according to middleware characteristics.
[0064] In this embodiment, middleware characteristics may include function types, communication protocols, dependencies, resource requirements, deployment architectures, security policies, and other characteristics.
[0065] S103: Detect whether the target middleware meets the preset startup conditions.
[0066] In this embodiment, the startup conditions may be that the prerequisite dependencies required for the middleware to run are complete (such as database connections, port availability, dependency library versions).
[0067] Optionally, it can be determined whether the target middleware meets the startup conditions through dependency checks, resource verification, and conflict detection.
[0068] Optionally, dependency checks may include verifying operating system dependencies (such as Java version), network port availability, storage path permissions, etc.
[0069] Optionally, resource verification may include verifying whether the CPU, memory, and disk space meet the middleware requirements.
[0070] Optionally, conflict detection may detect whether there are services with the same name or duplicate port occupations.
[0071] In an embodiment provided by the present application, based on the above solution, optionally, the detecting whether the target middleware meets the preset startup conditions includes:
[0072] Determine each dependency of the target middleware;
[0073] Detect whether each dependency of the target middleware is complete;
[0074] When each dependency of the target middleware is complete, determine that the target middleware meets the preset startup conditions.
[0075] In this embodiment, each dependency of the target middleware may be a set of software components required for the target middleware to run.
[0076] Optionally, detecting complete dependencies may mean detecting whether the file paths of each dependency are valid, whether the version compatibility meets the running requirements, and whether they are accessible, etc.; when the file paths of each dependency are valid, the version compatibility meets the running requirements, and they are accessible, it can be determined that each dependency passes the integrity detection, that is, each dependency of the target middleware is complete.
[0077] In this embodiment, when all dependencies pass the integrity detection, a startup permission flag bit can be generated, and the startup permission flag bit is used to indicate that the target middleware meets the startup conditions.
[0078] S104: When the target middleware meets the preset startup conditions, start the target middleware.
[0079] In this embodiment, starting the target middleware may be to load the middleware runtime environment, initialize the service process of the target middleware, and expose the interface externally.
[0080] Optionally, call a container engine or service orchestration tool to deploy a middleware instance, execute a startup script, and complete service registration.
[0081] S105: Receive a second middleware management instruction.
[0082] In this embodiment, the second middleware management instruction may be a control instruction for a running middleware, including an operation type (such as restart, stop, or uninstall, etc.) and a target instance identifier. The target instance identifier may be the identifier of the target middleware.
[0083] S106: In response to the second middleware management instruction, perform a management operation corresponding to the second middleware management instruction on the target middleware, and the management operation includes one of restarting the middleware service, stopping the middleware service, and uninstalling the middleware service.
[0084] In the embodiment provided in this embodiment, a first middleware management instruction can be received; in response to the first middleware management instruction, determine the target middleware to be started, and the target middleware is generated based on the middleware configuration information configured by the user; detect whether the target middleware meets the preset startup conditions; when the target middleware meets the preset startup conditions, start the target middleware; receive a second middleware management instruction; in response to the second middleware management instruction, perform a management operation corresponding to the second middleware management instruction on the target middleware, and the management operation includes one of restarting the middleware service, stopping the middleware service, and uninstalling the middleware service. Applying the method provided in the embodiments of the present application can effectively manage the entire life cycle of the middleware service.
[0085] In an embodiment provided by the present application, based on the above solution, optionally, after starting the target middleware, it further includes:
[0086] Monitoring the performance parameters and operating status corresponding to the target middleware.
[0087] In this embodiment, the performance parameters may include quantitative indicators reflecting the operating efficiency and resource consumption of the middleware. For example, CPU utilization rate, memory occupancy rate, number of active threads, request throughput, average response time, network bandwidth occupancy rate, disk I / O rate, cache hit rate, and database connection pool utilization rate, etc.
[0088] Optionally, the operating status may be a set of statuses characterizing the service availability and function integrity of the middleware, and may include service health status, transaction consistency status, error log status, etc.
[0089] In an embodiment provided by the present application, based on the above solution, optionally, the management operation is an operation to stop the middleware service;
[0090] Performing the management operation corresponding to the second middleware management instruction on the target middleware includes:
[0091] Determining the historical requests currently to be processed by the target middleware, and controlling the target middleware to stop receiving new requests;
[0092] After detecting that the historical requests received by the target middleware are processed, controlling the target middleware to stop running.
[0093] In this embodiment, the historical requests may be requests that the target middleware has received but not yet processed before receiving the stop instruction.
[0094] Optionally, controlling the target middleware to stop running may be to release the system resources occupied by the middleware, such as releasing resources such as memory and ports, terminating the service process, and canceling the service registration.
[0095] In this embodiment, the length of the request queue and the number of active threads may be detected periodically. If it is continuously detected N times that the queue is empty and the number of active threads is zero, it is determined that the historical requests received by the target middleware are processed.
[0096] In an embodiment provided by the present application, based on the above solution, optionally, the management operation is an operation to restart the middleware service;
[0097] Performing the management operation corresponding to the second middleware management instruction on the target middleware includes:
[0098] Starting the target service instance of the target middleware;
[0099] After the target service instance of the target middleware is started, stop the historical service instance of the target middleware from running to complete the restart of the middleware service.
[0100] In this embodiment, service update and recovery can be achieved by creating a target service instance and replacing the historical instance.
[0101] Optionally, the target service instance can be a new middleware instance generated according to the current configuration, including updated code, configuration, and dependency environment.
[0102] In this embodiment, when the target service instance is started, traffic can be gradually migrated from the historical service instance to the target service instance, a termination signal is sent to the historical service instance to trigger the cleanup logic, and when the active request count of the historical service instance is zero, control the historical service instance to stop running.
[0103] In an embodiment provided by this application, based on the above solution, optionally, the management operation is an operation to uninstall the middleware service;
[0104] Performing the management operation corresponding to the second middleware management instruction on the target middleware includes:
[0105] Uninstall the target middleware and release the resources occupied by the target middleware to complete the uninstallation of the middleware service.
[0106] In this embodiment, uninstalling the middleware service can be removing the middleware instance and its associated resources, such as software components, runtime data, and system resources.
[0107] This application provides a middleware service management solution based on full - life - cycle control, which can build a closed - loop management architecture covering the full life cycle of middleware services, including six core stages: service creation, startup, running monitoring, abnormal restart, active stop, and resource uninstallation. Each stage is seamlessly connected through standardized interfaces; a standardized process control module is established, including a configuration template library, operation verification rules, and version control mechanisms, to realize the automatic generation of basic description files during service creation, resource dependency and permission verification in the startup / stop stage, and atomic updates for version iteration; an automated execution engine is integrated, including a dynamic resource scheduler, a fault self - healing module, and an elastic scaling controller, to support SLA - driven resource allocation, automatic diagnosis and recovery of exceptions, and load - adaptive instance adjustment; a multi - dimensional intelligent monitoring system is built, through basic metric collection, APM call chain tracing, and security behavior analysis, combined with machine learning for correlation analysis, to generate a health score and drive decision - making; resource optimization strategies based on life - cycle stages are implemented, covering resource reservation during the creation period, dynamic allocation during the running period, and recycling and cleaning during the termination period, combined with utilization prediction and priority scheduling to improve resource utilization. Through the above technical solutions, this method realizes the systematic management of the full life cycle of middleware services, significantly improves management efficiency, service availability, and security, optimizes resource utilization, and is particularly suitable for cloud - native microservice architectures to meet high - concurrency and high - availability requirements.
[0108] See Figure 3 , which is a management flowchart of a middleware provided by this application, including the following steps:
[0109] Step 1: Create a middleware service.
[0110] In this embodiment, it may be necessary to define the specifications and requirements of the middleware service, including selecting the product name, version number, service name, business system, etc. At the same time, information such as configuration templates, service codes, and service discovery also needs to be configured. When creating the service, follow the standardized process to ensure consistency and repeatability.
[0111] Step 2: Start the middleware service.
[0112] In this embodiment, after the service creation is completed, the startup operation is performed. This usually involves executing configuration scripts, starting service processes, and ensuring that the service runs as expected. Use automated tools and scripts to reduce human errors, speed up the deployment, and ensure that each deployment is consistent.
[0113] Step 3: Running monitoring.
[0114] In this embodiment, after the service is started, it enters the running monitoring stage. This stage requires real - time monitoring of the performance and status of the service to ensure service stability.
[0115] Step 4: Restart the middleware service.
[0116] In this embodiment, an automated script or tool is used to restart the service to minimize the service interruption time.
[0117] Step 5: Stop the middleware service.
[0118] In this embodiment, while stopping the service, resource cleaning is performed, such as releasing memory and storage resources, to ensure that the resources can be used by other services.
[0119] Step 6: Uninstall the middleware service.
[0120] In this embodiment, when the service is no longer needed, the uninstall operation is performed. During the uninstallation process, all related files and configurations are thoroughly cleaned to ensure complete resource recovery.
[0121] Corresponding to Figure 1 the method described above, an embodiment of the present application further provides a middleware management device, which is applied to an electronic device and is used for Figure 1 the specific implementation of the method in Figure 4 as shown, and includes:
[0122] A first receiving unit 401, configured to receive a first middleware management instruction;
[0123] A determination unit 402, configured to determine a target middleware to be started in response to the first middleware management instruction, where the target middleware is generated based on middleware configuration information configured by a user;
[0124] A detection unit 403, configured to detect whether the target middleware meets a preset start condition;
[0125] A start unit 404, configured to start the target middleware when the target middleware meets the preset start condition;
[0126] A second receiving unit 405, configured to receive a second middleware management instruction;
[0127] An execution unit 406, configured to perform a management operation corresponding to the second middleware management instruction on the target middleware in response to the second middleware management instruction, where the management operation includes one of restarting the middleware service, stopping the middleware service, and uninstalling the middleware service.
[0128] In an embodiment provided by the present application, based on the above solution, optionally, the determination unit 402 includes:
[0129] A first receiving subunit, configured to receive middleware configuration information configured by a user;
[0130] The first execution subunit is configured to obtain a corresponding configuration template from a preset template library according to the middleware type and version in the middleware configuration information;
[0131] The second execution subunit is configured to run a configuration script to generate the target middleware based on the middleware configuration information and the configuration template, where the configuration script is pre-generated according to middleware characteristics.
[0132] In an embodiment provided by the present application, based on the above solution, optionally, the detection unit 403 includes:
[0133] The first determination subunit is configured to determine each dependency of the target middleware;
[0134] The detection subunit is configured to detect whether each dependency of the target middleware is complete;
[0135] The second determination subunit is configured to determine that the target middleware meets a preset start condition when each dependency of the target middleware is complete.
[0136] In an embodiment provided by the present application, based on the above solution, optionally, the apparatus further includes:
[0137] The monitoring unit is configured to monitor the performance parameters and running status corresponding to the target middleware.
[0138] In an embodiment provided by the present application, based on the above solution, optionally, the management operation is an operation to stop the middleware service;
[0139] The execution unit 406 includes:
[0140] The third determination subunit is configured to determine the historical requests currently to be processed by the target middleware and control the target middleware to stop receiving new requests;
[0141] The first control subunit is configured to control the target middleware to stop running after detecting that the historical requests received by the target middleware are processed.
[0142] In an embodiment provided by the present application, based on the above solution, optionally, the management operation is an operation to restart the middleware service;
[0143] The execution unit 406 includes:
[0144] The start subunit is configured to start the target service instance of the target middleware;
[0145] A second control subunit, configured to control the historical service instance of the target middleware to stop running after the target service instance of the target middleware is started, so as to complete the restart of the middleware service.
[0146] In an embodiment provided by the present application, based on the above solution, optionally, the management operation is an operation of uninstalling the middleware service;
[0147] The execution unit 406 includes:
[0148] A third execution subunit, configured to uninstall the target middleware and release the resources occupied by the target middleware, so as to complete the uninstallation of the middleware service.
[0149] The specific principles and execution processes of each unit and module in the middleware management device disclosed in the embodiments of the present application are the same as those of the middleware management method disclosed in the embodiments of the present application. For the corresponding parts in the middleware management method provided in the embodiments of the present application, reference can be made, and details will not be elaborated here.
[0150] The embodiments of the present application further provide a storage medium, which includes stored instructions. When the instructions run, the device where the storage medium is located is controlled to execute the above-mentioned middleware management method.
[0151] The embodiments of the present application further provide an electronic device, the structural schematic diagram of which is as Figure 5 shown, specifically including a memory 501 and one or more instructions 502. One or more instructions 502 are stored in the memory 501 and are configured to be executed by one or more processors 503 to execute the above-mentioned middleware management method.
[0152] It should be noted that the embodiments in this specification are all described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The same or similar parts among the embodiments can be referred to each other. For the device embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can refer to the description of the method embodiments.
[0153] Finally, it should also be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations.
[0154] For the convenience of description, when describing the above device, it is divided into various units according to functions for separate description. Of course, when implementing the present application, the functions of each unit can be realized in the same or multiple software and / or hardware.
[0155] From the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present application, in essence, or the part that makes contributions to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions for causing a computer device (which can be a personal computer, a server, etc.) to execute the methods described in various embodiments or some parts of the embodiments of the present application.
[0156] The above has introduced in detail a method for managing a middleware provided by the present application. Specific examples are used in this article to elaborate on the principle and implementation manner of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application; at the same time, for those of ordinary skill in the art, according to the idea of the present application, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to the present application.
Claims
1. A management method for middleware, characterized in that, It includes: Receiving a first middleware management instruction; In response to the first middleware management instruction, determining a target middleware to be started, where the target middleware is generated based on middleware configuration information configured by a user; Detecting whether the target middleware meets a preset start condition; When the target middleware meets the preset start condition, starting the target middleware; Receiving a second middleware management instruction; In response to the second middleware management instruction, performing a management operation corresponding to the second middleware management instruction on the target middleware, where the management operation includes one of restarting the middleware service, stopping the middleware service, and uninstalling the middleware service.
2. The method according to claim 1, characterized in that, The process of generating the target middleware based on middleware configuration information configured by a user includes: Receiving middleware configuration information configured by a user; According to the middleware type and version in the middleware configuration information, obtaining a corresponding configuration template from a preset template library; Running a configuration script to generate the target middleware based on the middleware configuration information and the configuration template, where the configuration script is pre-generated according to middleware characteristics.
3. The method according to claim 1, wherein The detecting whether the target middleware meets a preset start condition includes: Determining each dependency of the target middleware; Detecting whether each dependency of the target middleware is complete; When each dependency of the target middleware is complete, determining that the target middleware meets the preset start condition.
4. The method according to claim 1, wherein After starting the target middleware, it further includes: Monitoring performance parameters and running status corresponding to the target middleware.
5. The method according to claim 1, characterized in that, The management operation is an operation of stopping the middleware service; The performing a management operation corresponding to the second middleware management instruction on the target middleware includes: Determining historical requests currently to be processed by the target middleware, and controlling the target middleware to stop receiving new requests; After detecting that the historical requests received by the target middleware are processed, controlling the target middleware to stop running.
6. The method according to claim 1, characterized in that, The management operation is an operation of restarting the middleware service; The performing a management operation corresponding to the second middleware management instruction on the target middleware includes: Starting a target service instance of the target middleware; After the target service instance of the target middleware is started, controlling the historical service instance of the target middleware to stop running to complete restarting the middleware service.
7. The method according to claim 1, characterized in that The management operation is an operation of uninstalling the middleware service; The performing a management operation corresponding to the second middleware management instruction on the target middleware includes: Uninstalling the target middleware and releasing resources occupied by the target middleware to complete uninstalling the middleware service.
8. A management device for middleware, characterized in that It includes: A first receiving unit for receiving a first middleware management instruction; A determining unit for determining a target middleware to be started in response to the first middleware management instruction, where the target middleware is generated based on middleware configuration information configured by a user; A detecting unit for detecting whether the target middleware meets a preset start condition; A starting unit for starting the target middleware when the target middleware meets the preset start condition; A second receiving unit, configured to receive a second middleware management instruction; An execution unit, configured to, in response to the second middleware management instruction, perform a management operation corresponding to the second middleware management instruction on the target middleware, where the management operation includes one of restarting a middleware service, stopping a middleware service, and uninstalling a middleware service.
9. A storage medium, characterized in that, The storage medium includes stored instructions, wherein when the instructions are running, the device where the storage medium is located is controlled to execute the middleware management method according to any one of claims 1 to 7.
10. An electronic device, characterized in that, It includes a memory, and one or more instructions, wherein one or more instructions are stored in the memory and are configured to be executed by one or more processors to execute the middleware management method according to any one of claims 1 to 7.