Micro-service platform management and control method for lossless nano-management of different micro-service framework applications

Abstract

The invention provides a micro-service platform management and control method for lossless management of different micro-service framework applications, belongs to the technical field of micro-service management and control, and aims to solve the problems that the difference between an existing Java micro-service framework operation mechanism such as Apache Dubbo, SpringCloud and HSF and a governance model is large, cross-framework interconnection and intercommunication are difficult, service governance is scattered, and codes need to be modified. A JavaAgent plug-in is loaded when a micro-service JVM is started, a framework core component is enhanced in a class loading stage, service registration, discovery and calling processes are intercepted, the framework core component is converted into a unified data model and a communication protocol, and cross-framework intercommunication and unified management are realized in combination with a unified management and control center comprising a registration center, a configuration center, a monitoring center and a service management center. According to the method, business codes and framework source codes do not need to be modified, lossless management of the micro-service is realized, and the management and control efficiency and the system stability are improved.

Description

Technical Field

[0001] This invention relates to the field of microservice management technology, specifically to a microservice platform management method for seamless management of different microservice frameworks. Background Technology

[0002] With the widespread adoption of microservice architecture in enterprise systems, domestic enterprises often choose from various Java microservice frameworks based on their business needs, such as Apache Dubbo, Spring Cloud, HSF, and SOFAStack. These frameworks differ significantly in their operating mechanisms and governance models: Apache Dubbo emphasizes high-performance RPC calls, using binary protocols and a dedicated registry and discovery mechanism; Spring Cloud is based on HTTP / REST communication, relying on components such as Ribbon and Feign for service interaction; HSF, as a financial-grade framework, focuses on high availability and asynchronous call capabilities; and SOFAStack supports adaptation to multiple framework environments with its full-stack middleware.

[0003] In existing technologies, service governance in various frameworks largely relies on embedded SDKs—for example, Spring Cloud uses Resilience4j for circuit breaking and degradation, Dubbo relies on the Sentinel plugin for rate limiting, and HSF has its own independent governance solution. This approach exposes significant drawbacks in multi-framework hybrid deployment scenarios: First, cross-framework interconnection is difficult. Different frameworks have different protocols and registration mechanisms, requiring the development of additional gateways or adaptation layers to enable service calls, increasing development costs. Second, governance strategies are fragmented. Each framework configures governance rules independently, which can easily lead to system stability risks due to inconsistent rules. Furthermore, operations and maintenance personnel need to be familiar with the governance logic of multiple frameworks, resulting in high management complexity. Third, the cost of modification is high. Integrating new governance functions requires modifying business code or framework configurations, which may affect the operation of existing businesses or even introduce new faults. Fourth, cross-framework observability is poor. Each framework's link monitoring is independent, making it impossible to build a unified call link view, resulting in low efficiency in fault location. Summary of the Invention

[0004] The present invention aims to solve the problems mentioned in the background art by providing a microservice platform management method for seamless management of different microservice framework applications.

[0005] The specific technical solution is as follows: A method for seamlessly managing different microservice frameworks in a microservice platform includes the following steps: 1) Configure Agent plugins for each microservice deployed under different microservice frameworks. Each microservice loads the Agent plugin via JVM parameters when it starts up. 2) The Agent plugin enhances the core components of the target microservice framework during the class loading phase of each microservice and establishes a communication connection with the unified management and control center, which includes a registration center, a configuration center, a monitoring center, and a service governance center. 3) The Agent plugin intercepts the service registration and service discovery processes of each microservice, converts the native service registration information and service discovery requests of each microservice framework into a unified data model, and interacts with the registration center through the unified data model to complete the unified registration and unified discovery of each microservice. 4) The Agent plugin intercepts the service call process between microservices, extracts the service call context information and converts it into a unified communication protocol, and realizes the interconnection and interoperability between microservices under different microservice frameworks based on the unified communication protocol; 5) The service governance center obtains the preset unified service governance strategy from the configuration center, and injects the unified service governance strategy into the service call process of each microservice through the Agent plugin. The monitoring center collects the operation data and call link data of each microservice through the Agent plugin to realize unified management and status monitoring of each microservice.

[0006] The above-mentioned different microservice frameworks apply a lossless microservice platform management method, wherein the different microservice frameworks include at least two of the Apache Dubbo framework, Spring Cloud framework, HSF framework and SOFAStack framework.

[0007] The above-mentioned microservice frameworks apply a lossless microservice platform management method. In this method, the Agent plugin is a JavaAgent plugin. The Agent plugin enhances the core components of the target microservice framework by inserting interception logic based on bytecode enhancement technology. The core components include the microservice framework's registration component, discovery component, and RPC call component.

[0008] The above-mentioned different microservice frameworks apply a lossless microservice platform management method, wherein the unified service governance strategy includes at least three of the following: rate limiting control strategy, service circuit breaking strategy, service degradation strategy, canary release strategy, communication retry strategy, service authentication strategy, lossless online / offline strategy, push-out protection strategy, and fault injection strategy.

[0009] The above-mentioned microservice frameworks apply a lossless microservice platform management method. The execution process of the rate limiting control strategy includes: the Agent plugin collects QPS data and concurrent request data of each microservice interface and reports the collected data to the service governance center in real time; the service governance center, based on the rate limiting threshold issued by the configuration center, uses the Agent plugin to intercept or forward service call requests that exceed the rate limiting threshold using a token bucket algorithm or a leaky bucket algorithm.

[0010] The above-mentioned microservice frameworks apply a lossless microservice platform management method. The service circuit breaker strategy triggering process includes: the Agent plugin collects response time data and error rate data of each microservice call. When the response time exceeds a preset response time threshold or the error rate exceeds a preset error rate threshold, the service governance center triggers the service circuit breaker through the Agent plugin, and directs subsequent service call requests directly to the preset degradation processing logic.

[0011] The above-mentioned microservice frameworks apply a lossless microservice platform management method. The process of the monitoring center collecting call chain data includes: the agent plugin generates a globally unique TraceID at the initiating end of the service call, transmits the TraceID in each hop of the service call, and records the call time, call result, and service identification information of each hop; the agent plugin reports the call chain data carrying the TraceID to the monitoring center, and the monitoring center constructs a complete call chain view across microservice frameworks based on the TraceID.

[0012] The aforementioned microservice frameworks employ a lossless microservice platform management method. The execution process of the canary release strategy includes: the configuration center issuing canary release rules, which include the version information of the microservice to be released, the canary release ratio, and the target user identifier; the agent plugin intercepting service call requests directed to the microservice to be released, filtering out target user requests that meet the conditions according to the canary release rules, routing them to the new version of the microservice, and routing the remaining requests to the old version of the microservice; and the monitoring center monitoring the running status of the new version of the microservice in real time, adjusting the canary release ratio until full release is completed when the running status meets preset stability conditions.

[0013] The above-mentioned microservice frameworks apply a non-destructive microservice platform management method. In this method, the Agent plugin enhances each microservice without modifying the business code of each microservice or the source code of the target microservice framework. It only uses JVM runtime instrumentation to intercept and enhance the service registration, service discovery, and service call processes, thereby achieving non-destructive management of each microservice.

[0014] The above-mentioned microservice frameworks apply a lossless microservice platform management method. In this method, when the Agent plugin extracts the context information of the service call, it also obtains the priority identifier of the service call request. The service governance center allocates different resource quotas to service call requests of different priorities according to the priority identifier. The resource quota for high-priority service call requests is higher than that for low-priority service call requests, ensuring the normal operation of high-priority services during peak traffic periods.

[0015] The present invention has the following beneficial effects: 1. Solve the problem of cross-framework interconnection: By using an Agent to convert the unified communication protocol in the call chain, there is no need to develop additional adaptation layers or gateways. Microservices of different frameworks (such as Spring Cloud and HSF) can directly initiate calls, eliminating communication barriers in multi-framework mixed deployments and reducing the development cost of cross-framework integration.

[0016] 2. Achieve truly lossless management: The Agent enhances framework components only through JVM runtime instrumentation, without modifying business code or framework source code—ensuring the stability of the original business logic of microservices while avoiding the introduction of new faults due to code modifications; at the same time, microservices can be integrated into the management and control platform without adjusting the development process, significantly reducing the workload of modification and operation and maintenance.

[0017] 3. Unified service governance to improve cluster stability: Microservices across all frameworks share a single governance strategy (obtained from the configuration center), eliminating the need for separate rule configurations for Dubbo, Spring Cloud, etc., thus avoiding system risks caused by differences in governance strategies (such as overall overload caused by the lack of rate limiting in a certain framework); and the governance strategy takes effect in real time through the Agent, without the need to restart the service, ensuring business continuity.

[0018] 4. Improve cross-framework observability and reduce the difficulty of troubleshooting: The unified link view built on TraceID can penetrate the call boundaries of different frameworks and clearly present the complete call path from Spring Cloud service to Dubbo service and then to HSF service; operations and maintenance personnel do not need to switch multiple monitoring tools to quickly locate faulty nodes (such as the call latency of a certain SOFAStack service) and shorten the fault handling time.

[0019] 5. Prioritize core business operations and optimize resource utilization: After the Agent extracts the request priority identifier, the service governance center allocates more resource quotas (such as higher rate limiting thresholds) to high-priority requests (such as payments and orders). Even during peak traffic periods, core business operations will not be squeezed out by ordinary query requests, ensuring the response speed and availability of core business operations.

[0020] 6. Adaptable to multiple framework scenarios, expanding the scope of application: Covers mainstream domestic Java microservice frameworks such as Apache Dubbo, Spring Cloud, HSF, and SOFAStack, eliminating the need for customized management solutions for a single framework; In multi-framework hybrid deployment scenarios, enterprises can access the unified management platform without replacing existing frameworks, reducing technology selection and migration costs. Attached Figure Description

[0021] Figure 1 This is a block diagram illustrating a specific scheme for a microservice platform management method that enables lossless management of different microservice frameworks, as provided in embodiments of the present invention. Detailed Implementation

[0022] The technical solution of the present invention will be further described below with reference to the accompanying drawings and specific embodiments.

[0023] The accompanying drawings are for illustrative purposes only and are schematic diagrams, not actual images. They should not be construed as limiting the scope of this application. To better illustrate the embodiments of the present invention, some parts in the drawings may be omitted, enlarged, or reduced, and do not represent the actual dimensions of the product. It is understandable to those skilled in the art that some well-known structures and their descriptions may be omitted in the drawings.

[0024] In the accompanying drawings of the embodiments of the present invention, the same or similar reference numerals correspond to the same or similar components. In the description of the present invention, it should be understood that if terms such as "upper," "lower," "left," "right," "inner," and "outer" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, they are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, the terms used to describe positional relationships in the drawings are only for illustrative purposes and should not be construed as limiting the present application. For those skilled in the art, the specific meaning of the above terms can be understood according to the specific circumstances.

[0025] In the description of this invention, unless otherwise explicitly specified and limited, the term "connection" or similar designation indicating a connection between components should be interpreted broadly. For example, it can refer to a fixed connection, a detachable connection, or an integral part; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium; it can refer to the internal communication between two components or the interaction between two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0026] Example This embodiment provides a method for managing microservice platforms that applies lossless management to different microservice frameworks, such as... Figure 1As shown, it includes the following steps: 1) Configure Agent plugins for each microservice deployed under different microservice frameworks. Each microservice loads the Agent plugin via JVM parameters when it starts up. 2) During the class loading phase of each microservice, the Agent plugin enhances the core components of the target microservice framework and establishes a communication connection with the unified management and control center, which includes the registration center, configuration center, monitoring center, and service governance center. 3) The Agent plugin intercepts the service registration and service discovery processes of each microservice, converts the native service registration information and service discovery requests of each microservice framework into a unified data model, and interacts with the registry center through the unified data model to complete the unified registration and unified discovery of each microservice. 4) The Agent plugin intercepts the service call process between various microservices, extracts the context information of the service call and converts it into a unified communication protocol, and realizes the interconnection and interoperability between microservices under different microservice frameworks based on the unified communication protocol; 5) The service governance center obtains the preset unified service governance policy from the configuration center and injects the unified service governance policy into the service call process of each microservice through the Agent plugin. The monitoring center collects the operation data and call chain data of each microservice through the Agent plugin to achieve unified management and status monitoring of each microservice.

[0027] This solution enhances core components during the class loading phase by configuring Agent plugins for microservices across different microservice frameworks. It intercepts service registration, discovery, and invocation processes, converting them into a unified data model and communication protocol. Simultaneously, it integrates with a unified management and control center for governance and monitoring. The technical benefits are as follows: unified registration and discovery of microservices across different frameworks can be achieved without modifying the business code or framework source code of the microservices, solving the problem of cross-framework interoperability. Furthermore, by applying unified service governance policies and collecting operational data through the unified management and control center, it addresses the issues of fragmented service governance and inconsistent control in multi-framework environments. Ultimately, it achieves seamless management of applications across different microservice frameworks, ensuring the stability of the original operational logic of the business system.

[0028] Specifically, in this embodiment, the different microservice frameworks include at least two of the following: Apache Dubbo framework, Spring Cloud framework, HSF framework, and SOFAStack framework.

[0029] This solution specifies at least two of the following microservice frameworks: Apache Dubbo, Spring Cloud, HSF, and SOFAStack. It covers the mainstream Java microservice frameworks and its technical advantages include: adaptability to multiple microservice frameworks commonly used by domestic enterprises; elimination of the need for separate management solutions for individual frameworks; expanded applicability of microservice platform management methods; effective resolution of unified management issues in multi-framework deployment scenarios; and reduced management costs for enterprises in multi-framework environments.

[0030] Specifically, in this embodiment, the Agent plugin is a JavaAgent plugin. The Agent plugin enhances the core components of the target microservice framework by inserting interception logic based on bytecode enhancement technology. The core components include the microservice framework's registration component, discovery component, and RPC call component.

[0031] This solution limits the Agent plugin to JavaAgent, employing bytecode enhancement technology to insert interception logic during the class loading phase. The core enhanced components are explicitly defined as the registration, discovery, and RPC call components. Combining the runtime instrumentation characteristics of JavaAgent with the non-intrusive nature of bytecode enhancement, the technical effects are: non-intrusive enhancement is achieved during the microservice JVM runtime, without modifying the microservice or framework source code, ensuring the original microservice operating mechanism remains unaffected; simultaneously, it accurately intercepts key processes such as service registration, discovery, and RPC calls, providing a reliable execution foundation for subsequent unified data conversion, protocol adaptation, and service governance logic injection, ensuring the effective implementation of unified management and control functions.

[0032] Specifically, in this embodiment, the unified service governance strategy includes at least three of the following: rate limiting control strategy, service circuit breaking strategy, service degradation strategy, canary release strategy, communication retry strategy, service authentication strategy, lossless online / offline strategy, push-to-free protection strategy, and fault injection strategy.

[0033] This solution explicitly defines a unified service governance strategy, including at least three types: rate limiting, service circuit breaking, service degradation, and canary releases. Addressing the issue in existing technologies where each microservice framework relies on its own independent governance scheme, resulting in fragmented and unified rules, this solution achieves the following technical benefits: it enables microservices under different microservice frameworks to share a single service governance strategy, eliminating the need to configure governance rules separately for each framework, thus simplifying the configuration and management process of service governance; simultaneously, it ensures consistency of service governance rules across different frameworks, avoiding system stability risks caused by differences in governance strategies, and improving the overall fault tolerance and operational stability of the microservice cluster.

[0034] Specifically, in this embodiment, the execution process of the rate limiting control strategy includes: the Agent plugin collects the QPS data and concurrent request data of each microservice interface, and reports the collected data to the service governance center in real time; the service governance center, based on the rate limiting threshold issued by the configuration center, uses the Agent plugin to intercept or forward service call requests that exceed the rate limiting threshold using the token bucket algorithm or the leaky bucket algorithm.

[0035] This solution defines a rate-limiting control strategy that collects QPS and concurrent request data through an Agent plugin. The service governance center uses a token bucket or leaky bucket algorithm to intercept requests exceeding the rate-limiting threshold. Addressing the issue of service overload caused by sudden traffic surges in existing technologies, the solution achieves the following: real-time monitoring of traffic changes at microservice interfaces; precise control of request volume based on preset thresholds to prevent microservice failures due to traffic exceeding capacity; and smooth traffic control through token bucket or leaky bucket algorithms to prevent sudden traffic surges from impacting services, ensuring the normal operation of core functions of microservices under high-traffic scenarios and reducing the risk of business interruption due to traffic overload.

[0036] Specifically, in this embodiment, the service circuit breaker strategy triggering process includes: the Agent plugin collects response time data and error rate data of each microservice call; when the response time exceeds the preset response time threshold or the error rate exceeds the preset error rate threshold, the service governance center triggers the service circuit breaker through the Agent plugin, and directs subsequent service call requests directly to the preset degradation processing logic.

[0037] This solution limits the service circuit breaker strategy to using an agent plugin to track response time and error rate. When these thresholds are exceeded, a circuit breaker is triggered, and requests are redirected to degradation logic. Addressing the issue of cascading failures caused by downstream service anomalies in existing technologies, its technical effects are: timely identification of abnormal situations in service calls (such as response timeouts or excessively high error rates), rapid termination of invalid calls to abnormal services through the circuit breaker mechanism to avoid resource waste; and ensuring the availability of core business functions through degradation logic, preventing downstream service anomalies from propagating upstream, effectively blocking the propagation path of cascading failures, and improving the fault tolerance of the microservice cluster.

[0038] Specifically, in this embodiment, the process of the monitoring center collecting call chain data includes: the Agent plugin generates a globally unique TraceID at the initiating end of the service call, transmits the TraceID in each hop of the service call, and records the call time, call result and service identification information of each hop; the Agent plugin reports the call chain data carrying the TraceID to the monitoring center, and the monitoring center builds a complete call chain view across the microservice framework based on the TraceID.

[0039] This solution requires the monitoring center to generate TraceIDs, transmit call data, and build a cross-framework call chain view via an Agent plugin. Addressing the challenge of achieving unified link monitoring across microservice frameworks in existing technologies, its technical advantages include: penetrating the call boundaries of different microservice frameworks, fully tracing the call paths between microservices, and clearly presenting information such as call time consumption, call results, and service identifiers; the unified link view built based on TraceIDs helps operations personnel quickly locate faulty nodes in cross-framework calls, reducing the difficulty of troubleshooting and improving the observability of the microservice cluster.

[0040] Specifically, in this embodiment, the execution process of the canary release strategy includes: the configuration center issuing canary release rules, which include the version information of the microservice to be released, the canary release ratio, and the target user identifier; the Agent plugin intercepting service call requests directed to the microservice to be released, filtering out target user requests that meet the conditions according to the canary release rules, routing them to the new version microservice, and routing the remaining requests to the old version microservice; the monitoring center monitoring the running status of the new version microservice in real time, and when the running status meets the preset stability conditions, the configuration center adjusting the canary release ratio until the full release is completed.

[0041] This solution limits the canary release strategy to a configuration center by issuing rules, with the Agent plugin routing requests according to these rules. The monitoring center then adjusts the rollout ratio after verifying stability. Addressing the high risk of full-scale releases of new versions in existing technologies, this solution offers the following advantages: New version microservices can be released to a subset of users in batches, with real-time stability verification through the monitoring center, preventing version defects from affecting all users during a full release; simultaneously, the rollout ratio can be flexibly adjusted based on stability, achieving a smooth launch of the new version, reducing the impact of version iterations on business continuity, and improving the security and reliability of service releases.

[0042] Specifically, in this embodiment, the Agent plugin enhances each microservice without modifying the business code of each microservice or the source code of the target microservice framework. It only uses JVM runtime instrumentation to intercept and enhance the service registration, service discovery, and service call processes, thereby achieving seamless management of each microservice.

[0043] This solution emphasizes that the Agent plugin enhancement process does not modify business code or framework source code, but only achieves interception and enhancement through JVM runtime instrumentation. Addressing the issue of high costs associated with code modification for service governance integration in existing technologies, its technical advantages are: It completely achieves non-intrusive microservice management without requiring adjustments to existing business logic or underlying framework code, significantly reducing the workload and operational costs of integrating microservices into a unified management platform; simultaneously, it avoids new faults that may be introduced by code modifications, ensuring the stability of the original microservice functionality and guaranteeing the continuous normal operation of business systems when integrating management capabilities.

[0044] Specifically, in this embodiment, when the Agent plugin extracts the context information of the service call, it also obtains the priority identifier of the service call request. The service governance center allocates different resource quotas to service call requests of different priorities according to the priority identifier. The resource quota for high-priority service call requests is higher than that for low-priority service call requests, ensuring the normal operation of high-priority services during peak traffic periods.

[0045] This solution limits the Agent plugin to extract request priority identifiers, and the service governance center allocates resources according to priority, with higher priority requests receiving higher resource quotas. Addressing the issues in existing technologies where resource allocation cannot differentiate between business importance and core business processes are easily affected by ordinary requests, this solution achieves the following: it prioritizes resource supply for high-priority businesses (such as payment and order processing), ensuring sufficient resource support even during peak traffic periods, preventing ordinary requests from crowding out resources and causing service anomalies; and it optimizes resource utilization efficiency through differentiated resource allocation, ensuring the stability and response speed of core businesses and improving the overall service quality of the business system.

[0046] In summary, the microservice platform management method for seamlessly managing different microservice frameworks provided in this embodiment achieves seamless management and unified control over different microservice frameworks through the collaboration of the JavaAgent plugin and a unified management and control center (including a registration center, configuration center, monitoring center, and service governance center). The specific principle is as follows: 1. Non-intrusive enhancement of the Agent plugin: When each microservice starts, the JavaAgent plugin is loaded via JVM parameters; during the microservice class loading phase, the Agent uses bytecode enhancement technology to insert interception logic into the core components of the framework (registration component, discovery component, RPC call component) - this process does not modify the microservice business code or the framework source code, but only extends the functionality of the components at runtime.

[0047] 2. Unified Registration and Discovery: When a microservice performs service registration (reporting its own information to the registry center) or service discovery (subscribing to information about other services), the Agent intercepts the native registration / discovery request, converts framework-specific information (such as Dubbo's service interface name and Spring Cloud's application name) into a unified data model, and then interacts with the registry center through the unified data model; ultimately, it achieves a "unified presentation" of microservices from different frameworks in the registry center, and each microservice can obtain cross-framework service information through the unified data model.

[0048] 3. Cross-framework call adaptation: When a microservice initiates a cross-framework call (such as a Spring Cloud service calling an HSF service), the Agent intercepts the call request, extracts the call context (service name, interface name, request parameters) and converts it into a unified communication protocol; at the same time, on the receiving end, the Agent converts the unified protocol into the framework's native protocol to ensure that the call is executed normally - which is equivalent to the Agent acting as a "protocol converter" in the call chain, enabling direct interoperability between services of different frameworks.

[0049] 4. Unified Service Governance Injection: The configuration center pre-stores unified service governance policies (rate limiting, circuit breaking, canary release, etc.); after obtaining the policies from the configuration center, the service governance center injects the policies into the service call process through the Agent: for example, the Agent collects interface QPS data in real time, and if it exceeds the rate limiting threshold, it intercepts requests according to the token bucket / leaky bucket algorithm; if the service call error rate exceeds the standard, it triggers the circuit breaker and leads to degradation logic.

[0050] 5. Cross-framework link monitoring: The agent generates a globally unique TraceID at the call initiation end, continuously transmits the TraceID during the call, and records the call time, result, and service identifier of each hop; the agent reports the link data carrying the TraceID to the monitoring center, and the monitoring center connects the cross-framework call nodes based on the TraceID to build a complete call link view.

[0051] How to use 1. Preliminary configuration preparation 1.1 Configure the JavaAgent plugin for each microservice: Add JVM parameters (such as -javaagent:path / StarringAgent.jar) to the microservice startup script to specify the Agent plugin path; at the same time, fill in the address of the unified management center (registration center, configuration center, etc.) in the Agent configuration file to ensure that the Agent can communicate normally with the management center.

[0052] 1.2 Configure a unified management and control center: Set unified service governance policies in the configuration center, such as setting rate limiting thresholds for payment services (e.g., upper limit of interface QPS), circuit breaker triggering conditions (e.g., response timeout time, upper limit of error rate), and canary release rules (e.g., new version release ratio, target user identifier); configure service metadata storage rules in the registry center to ensure compatibility with the unified data model of different frameworks.

[0053] 2. Microservice startup and management 2.1 Start each microservice: When a microservice starts, the JavaAgent plugin is automatically loaded. During the class loading phase, the Agent enhances the core components of the framework, then intercepts service registration requests and reports the unified data model to the registration center, completing "lossless management"—this process requires no manual intervention, and the original startup process of the microservice remains unchanged.

[0054] 2.2 Verify the management status: Check whether each microservice (regardless of framework type) is registered normally through the registry center; confirm whether the Agent has successfully reported the basic operation data of the microservice (such as service online status and interface call volume) through the monitoring center.

[0055] 3. Runtime Management and Maintenance 3.1 Service Invocation and Governance Execution: When a microservice initiates a cross-framework call, the Agent automatically completes the protocol conversion and governance strategy execution (such as rate limiting and circuit breaking); operations and maintenance personnel can view the governance effect in real time through the monitoring center (such as the number of blocked requests and the number of circuit break triggers).

[0056] 3.2 Policy Adjustment and Canary Release: If the governance policy needs to be modified, the rules can be updated directly in the configuration center. The Agent will obtain the new policy in real time and make it effective without restarting the microservice. When performing canary release, the release ratio is adjusted in the configuration center. The Agent will route some requests to the new version service according to the rules. The monitoring center tracks the running status of the new version. After it is stable, the release ratio is gradually increased until full release.

[0057] 3.3 Troubleshooting and Handling: When the monitoring center displays service anomalies, locate the faulty node by calling the link view across frameworks (e.g., a Dubbo service response timeout); if a circuit breaker is triggered, the reason for the circuit breaker can be viewed in the service governance center (e.g., error rate exceeding the standard), and the circuit breaker status can be reset through the configuration center after repair.

[0058] Overall technical effect The technical effectiveness of this method is derived from the core solutions of "non-intrusive enhancement of JavaAgent" and "unified management center collaboration," as detailed below: 1. Solve the problem of cross-framework interconnection: By using an Agent to convert the unified communication protocol in the call chain, there is no need to develop additional adaptation layers or gateways. Microservices of different frameworks (such as Spring Cloud and HSF) can directly initiate calls, eliminating communication barriers in multi-framework mixed deployments and reducing the development cost of cross-framework integration.

[0059] 2. Achieve truly lossless management: The Agent enhances framework components only through JVM runtime instrumentation, without modifying business code or framework source code—ensuring the stability of the original business logic of microservices while avoiding the introduction of new faults due to code modifications; at the same time, microservices can be integrated into the management and control platform without adjusting the development process, significantly reducing the workload of modification and operation and maintenance.

[0060] 3. Unified service governance to improve cluster stability: Microservices across all frameworks share a single governance strategy (obtained from the configuration center), eliminating the need for separate rule configurations for Dubbo, Spring Cloud, etc., thus avoiding system risks caused by differences in governance strategies (such as overall overload caused by the lack of rate limiting in a certain framework); and the governance strategy takes effect in real time through the Agent, without the need to restart the service, ensuring business continuity.

[0061] 4. Improve cross-framework observability and reduce the difficulty of troubleshooting: The unified link view built on TraceID can penetrate the call boundaries of different frameworks and clearly present the complete call path from Spring Cloud service to Dubbo service and then to HSF service; operations and maintenance personnel do not need to switch multiple monitoring tools to quickly locate faulty nodes (such as the call latency of a certain SOFAStack service) and shorten the fault handling time.

[0062] 5. Prioritize core business operations and optimize resource utilization: After the Agent extracts the request priority identifier, the service governance center allocates more resource quotas (such as higher rate limiting thresholds) to high-priority requests (such as payments and orders). Even during peak traffic periods, core business operations will not be squeezed out by ordinary query requests, ensuring the response speed and availability of core business operations.

[0063] 6. Adaptable to multiple framework scenarios, expanding the scope of application: Covers mainstream domestic Java microservice frameworks such as Apache Dubbo, Spring Cloud, HSF, and SOFAStack, eliminating the need for customized management solutions for a single framework; In multi-framework hybrid deployment scenarios, enterprises can access the unified management platform without replacing existing frameworks, reducing technology selection and migration costs.

[0064] The above are merely preferred embodiments of the present invention and are not intended to limit the implementation methods and protection scope of the present invention. Those skilled in the art should recognize that any equivalent substitutions and obvious changes made based on the description and illustrations of the present invention should be included within the protection scope of the present invention.

Claims

1. A microservice platform management and control method for seamless management of different microservice frameworks, characterized in that, Includes the following steps: 1) Configure Agent plugins for each microservice deployed under different microservice frameworks. Each microservice loads the Agent plugin via JVM parameters when it starts up. 2) The Agent plugin enhances the core components of the target microservice framework during the class loading phase of each microservice and establishes a communication connection with the unified management and control center, which includes a registration center, a configuration center, a monitoring center, and a service governance center. 3) The Agent plugin intercepts the service registration and service discovery processes of each microservice, converts the native service registration information and service discovery requests of each microservice framework into a unified data model, and interacts with the registration center through the unified data model to complete the unified registration and unified discovery of each microservice. 4) The Agent plugin intercepts the service call process between microservices, extracts the service call context information and converts it into a unified communication protocol, and realizes the interconnection and interoperability between microservices under different microservice frameworks based on the unified communication protocol; 5) The service governance center obtains the preset unified service governance strategy from the configuration center, and injects the unified service governance strategy into the service call process of each microservice through the Agent plugin. The monitoring center collects the operation data and call link data of each microservice through the Agent plugin to realize unified management and status monitoring of each microservice.

2. The microservice platform management and control method for lossless management of different microservice frameworks according to claim 1, characterized in that, The different microservice frameworks include at least two of the following: Apache Dubbo, Spring Cloud, HSF, and SOFAStack.

3. The microservice platform management and control method for lossless management of different microservice frameworks according to claim 1, characterized in that, The Agent plugin is a JavaAgent plugin. The Agent plugin enhances the core components of the target microservice framework by inserting interception logic based on bytecode enhancement technology. The core components include the microservice framework's registration component, discovery component, and RPC call component.

4. The microservice platform management and control method for lossless management of different microservice frameworks according to claim 1, characterized in that, The unified service governance strategy includes at least three of the following: rate limiting strategy, service circuit breaker strategy, service degradation strategy, canary release strategy, communication retry strategy, service authentication strategy, lossless online / offline strategy, push-out protection strategy, and fault injection strategy.

5. The microservice platform management and control method for lossless management of different microservice frameworks according to claim 4, characterized in that, The execution process of the rate limiting control strategy includes: the Agent plugin collects the QPS data and concurrent request data of each microservice interface, and reports the collected data to the service governance center in real time; the service governance center, based on the rate limiting threshold issued by the configuration center, uses the Agent plugin to intercept or forward service call requests that exceed the rate limiting threshold using the token bucket algorithm or the leaky bucket algorithm.

6. The microservice platform management method for lossless management of different microservice frameworks according to claim 4, characterized in that, The service circuit breaker strategy triggering process includes: the Agent plugin collects response time data and error rate data of each microservice call; when the response time exceeds a preset response time threshold or the error rate exceeds a preset error rate threshold, the service governance center triggers the service circuit breaker through the Agent plugin, and directs subsequent service call requests directly to the preset degradation processing logic.

7. The microservice platform management and control method for lossless management of different microservice frameworks according to claim 1, characterized in that, The process of the monitoring center collecting call chain data includes: the agent plugin generates a globally unique TraceID at the initiating end of the service call, transmits the TraceID in each hop of the service call, and records the call time, call result and service identification information of each hop; the agent plugin reports the call chain data carrying the TraceID to the monitoring center, and the monitoring center constructs a complete call chain view across the microservice framework based on the TraceID.

8. The microservice platform management and control method for lossless management of different microservice frameworks according to claim 4, characterized in that, The execution process of the canary release strategy includes: the configuration center issuing canary release rules, which include the version information of the microservice to be released, the canary release ratio, and the target user identifier; the agent plugin intercepting service call requests directed to the microservice to be released, filtering out target user requests that meet the conditions according to the canary release rules, routing them to the new version microservice, and routing the remaining requests to the old version microservice; the monitoring center monitoring the running status of the new version microservice in real time, and when the running status meets the preset stability conditions, the configuration center adjusting the canary release ratio until the full release is completed.

9. The microservice platform management and control method for lossless management of different microservice frameworks according to claim 1, characterized in that, During the process of enhancing each microservice, the Agent plugin does not modify the business code of each microservice or the source code of the target microservice framework. It only uses JVM runtime instrumentation to intercept and enhance the service registration, service discovery, and service call processes, thereby achieving lossless management of each microservice.

10. The microservice platform management method for lossless management of different microservice frameworks according to claim 1, characterized in that, When the Agent plugin extracts the context information of the service call, it also obtains the priority identifier of the service call request. The service governance center allocates different resource quotas to service call requests of different priorities according to the priority identifier. The resource quota for high-priority service call requests is higher than that for low-priority service call requests, ensuring the normal operation of high-priority services during peak traffic periods.

Images