Service deployment method and apparatus, electronic device, medium, and program product

Abstract

This disclosure presents service deployment methods, apparatus, electronic devices, media, and program products. One specific implementation of the method includes: performing interface tracking on each application interface in a set of application interfaces corresponding to a target application to obtain an interface tracking dataset; performing traffic statistics on the interface tracking dataset according to preset service splitting configuration information to obtain a traffic statistics information set; performing dynamic splitting processing on the target application based on the traffic statistics information set and the preset service splitting configuration information to obtain an application service information set and a service interface set; and sending the preset service splitting configuration information, the application service information set, and the service interface set to a service deployment terminal for dynamic deployment. This implementation is related to service splitting, which can improve the flexibility and efficiency of target application splitting, and since the splitting is interface-based, it can split individual interfaces, reducing resource waste.

Description

Technical Field

[0001] Embodiments of this disclosure relate to the field of computer technology, and more specifically to service deployment methods, apparatus, electronic devices, media, and program products. Background Technology

[0002] Service decomposition refers to breaking down an application into a set of small, loosely coupled services, each built around a specific business capability. Service decomposition requires functional, modular, and interface decomposition during the service architecture design or upgrade iteration phase. Once the service architecture is designed, it remains unchanged. If changes are needed, a complete redesign, review, coding, and deployment process must be undertaken from scratch. For application service decomposition, the typical approach is to statically decompose the application during the architecture design phase, resulting in a microservice architecture. Then, when there is a sudden surge in traffic to interfaces within the microservice structure, the application is scaled up or down using the HPA (Horizontal Pod Autoscaler) algorithm.

[0003] However, the inventors discovered that when using the above method to split application services, the following technical problems often arise:

[0004] Since static partitioning is determined during the architecture design phase and cannot be dynamically adjusted in subsequent applications, any adjustments to the architecture require redesigning from the design phase, resulting in long application service partitioning times and significant partitioning difficulties. Furthermore, the HPA algorithm scales up and down the entire application as a whole. When a single application interface experiences a traffic surge, other interfaces that do not experience a traffic surge will also scale up, leading to resource waste and failing to resolve the issue of resource contention between interfaces.

[0005] The information disclosed in this background section is only intended to enhance the understanding of the background of the inventive concept, and therefore may contain information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0006] The summary portion of this disclosure is intended to provide a brief overview of the concepts, which will be described in detail in the detailed description portion. This summary portion is not intended to identify key or essential features of the claimed technical solutions, nor is it intended to limit the scope of the claimed technical solutions.

[0007] Some embodiments of this disclosure provide service deployment methods, apparatuses, electronic devices, media, and program products to address one or more of the technical problems mentioned in the background section above.

[0008] In a first aspect, some embodiments of this disclosure provide a service deployment method, including: performing interface tracking on each application interface in the application interface set corresponding to the target application to generate interface tracking data and obtain an interface tracking dataset; performing traffic statistics on the interface tracking dataset according to preset service splitting configuration information to obtain a traffic statistics information set; performing dynamic splitting processing on the target application according to the traffic statistics information set and the preset service splitting configuration information to obtain an application service information set and a service interface set; and sending the preset service splitting configuration information, the application service information set, and the service interface set to a service deployment terminal for dynamic deployment.

[0009] Optionally, the above-mentioned traffic statistics on the interface tracking data set based on the preset service splitting configuration information to obtain a traffic statistics information set includes: in response to determining that the preset service splitting configuration information is application interface splitting information, determining the interface tracking data corresponding to the preset service splitting configuration information as the target interface tracking data; and performing traffic statistics on the target interface tracking data based on the statistical time period included in the preset service splitting configuration information to obtain traffic statistics information.

[0010] Optionally, the above-mentioned traffic statistics on the interface tracking dataset based on the preset service splitting configuration information to obtain a traffic statistics information set includes: in response to determining that the preset service splitting configuration information is application splitting information, determining at least one interface tracking dataset corresponding to the target application; and performing traffic statistics on the at least one interface tracking dataset based on the statistical time period included in the preset service splitting configuration information to obtain traffic statistics information.

[0011] Optionally, the above-mentioned dynamic splitting process of the target application based on the traffic statistics information set and the preset service splitting configuration information to obtain an application service information set and a service interface set includes: in response to determining that the preset service splitting configuration information is application interface splitting information, splitting the process corresponding to at least one application interface corresponding to the preset service splitting configuration information from the target application to obtain a split service information set; scaling up or down the service set corresponding to the split service information set according to the preset service splitting configuration information to obtain an application service information set; and taking the application interface group corresponding to each application service information in the application service information set as a service interface to obtain a service interface set.

[0012] Optionally, the above-mentioned dynamic splitting of the target application based on the traffic statistics information set and the preset service splitting configuration information to obtain an application service information set and a service interface set includes: in response to determining that the preset service splitting configuration information is application splitting information, scaling up or down the process corresponding to at least one application interface according to the preset service splitting configuration information to obtain a scaled-down application interface set as a service interface set, wherein the at least one application interface corresponds to the preset service splitting configuration information; and determining the target application as target service information as the application service information set.

[0013] Optionally, before performing interface tracking on each application interface corresponding to the application interface set in the target application to generate interface tracking data and obtain the interface tracking dataset, the process includes: registering the application interface set corresponding to the target application and the target application; in response to determining that the application interface set and the target application are successfully registered, performing interface tracking on each application interface in the application interface set corresponding to the target application to generate interface tracking data and obtain the interface tracking dataset.

[0014] Optionally, the above registration of the application interface set corresponding to the target application and the target application includes: adding the interface path set corresponding to the application interface set and the application identifier of the target application to the environment configuration file to obtain the added environment configuration file; in response to detecting that the application agent corresponding to the target application has started successfully, registering the interface path set and the application identifier to the service processing end according to the added environment configuration file.

[0015] Optionally, the above-mentioned registration of the application interface set corresponding to the target application and the target application includes: determining the service registration file corresponding to the service processing terminal; adding the interface path set corresponding to the application interface set and the application identifier of the target application to the service registration file to register the application interface set and the target application.

[0016] Optionally, the above-mentioned method of performing interface tracking on each application interface in the application interface set corresponding to the target application to generate interface tracking data and obtain an interface tracking dataset includes: in response to detecting that the target application has started successfully, loading an application agent on the application virtual machine corresponding to the target application; in response to detecting that the application virtual machine has started successfully, executing the target function in the application agent to perform interface tracking on each application interface in the application interface set and obtain an interface tracking dataset.

[0017] Secondly, some embodiments of this disclosure provide a service deployment apparatus, including: an interface tracking unit configured to perform interface tracking on each application interface in an application interface set corresponding to a target application to generate interface tracking data and obtain an interface tracking dataset; a traffic statistics unit configured to perform traffic statistics on the interface tracking dataset according to preset service splitting configuration information to obtain a traffic statistics information set; a dynamic splitting unit configured to perform dynamic splitting processing on the target application according to the traffic statistics information set and the preset service splitting configuration information to obtain an application service information set and a service interface set; and a sending unit configured to send the preset service splitting configuration information, the application service information set, and the service interface set to a service deployment end for dynamic deployment by the service deployment end.

[0018] Optionally, the traffic statistics unit can be configured to: in response to determining that the above-mentioned preset service splitting configuration information is application interface splitting information, determine the interface tracking data corresponding to the above-mentioned preset service splitting configuration information as target interface tracking data; and perform traffic statistics on the above-mentioned target interface tracking data according to the statistical time period included in the above-mentioned preset service splitting configuration information to obtain traffic statistics information.

[0019] Optionally, the traffic statistics unit can be configured to: in response to determining that the above-mentioned preset service splitting configuration information is application splitting information, determine at least one interface tracking data set corresponding to the above-mentioned target application; and perform traffic statistics on the above-mentioned at least one interface tracking data set according to the statistical time period included in the above-mentioned preset service splitting configuration information to obtain traffic statistics information.

[0020] Optionally, the dynamic splitting unit can be configured to: in response to determining that the preset service splitting configuration information is application interface splitting information, split the process corresponding to at least one application interface corresponding to the preset service splitting configuration information from the target application to obtain a split service information set; perform scaling processing on the service set corresponding to the split service information set according to the preset service splitting configuration information to obtain an application service information set; and take the application interface group corresponding to each application service information in the application service information set as a service interface to obtain a service interface set.

[0021] Optionally, the dynamic splitting unit can be configured to: in response to determining that the above-mentioned preset service splitting configuration information is application splitting information, perform scaling up or down processing on the process corresponding to at least one application interface according to the above-mentioned preset service splitting configuration information to obtain a scaled-down application interface set as a service interface set, wherein the above-mentioned at least one application interface is corresponding to the above-mentioned preset service splitting configuration information; and determine the above-mentioned target application as target service information as an application service information set.

[0022] Optionally, the interface tracking unit can be configured to: register the application interface set corresponding to the target application and the target application; in response to determining that the application interface set and the target application are successfully registered, perform interface tracking on each application interface in the application interface set corresponding to the target application to generate interface tracking data and obtain an interface tracking dataset.

[0023] Optionally, the interface tracking unit can be configured to: add the interface path set corresponding to the above application interface set and the application identifier of the above target application to the environment configuration file to obtain the added environment configuration file; in response to detecting that the application agent corresponding to the above target application has started successfully, register the above interface path set and the above application identifier to the service processing end according to the added environment configuration file.

[0024] Optionally, the interface tracking unit can be configured to: determine the service registration file corresponding to the above service processing terminal; add the interface path set corresponding to the above application interface set and the application identifier of the above target application to the above service registration file, so as to register the above application interface set and the above target application.

[0025] Optionally, the interface tracking unit can be configured to: in response to detecting that the target application has started successfully, load an application agent on the application virtual machine corresponding to the target application; in response to detecting that the application virtual machine has started successfully, execute the target function in the application agent to perform interface tracking on each application interface in the application interface set to obtain an interface tracking dataset.

[0026] Thirdly, some embodiments of this disclosure provide an electronic device, including: one or more processors; and a storage device having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any of the implementations of the first aspect above.

[0027] Fourthly, some embodiments of this disclosure provide a computer-readable medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the method described in any of the implementations of the first aspect above.

[0028] Fifthly, some embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, implements the method described in any of the implementations of the first aspect above.

[0029] The above embodiments of this disclosure have the following beneficial effects: the service deployment methods of some embodiments of this disclosure can improve the flexibility and efficiency of target application splitting, and the splitting is based on application interfaces, allowing for the splitting of individual interfaces, which can reduce resource waste. Specifically, the reasons for the long splitting time, high splitting difficulty, and resource waste of related application services, and the inability to solve the problem of resource contention between interfaces, are as follows: since static splitting is determined in the architecture design stage and cannot be dynamically adjusted in subsequent applications, if the architecture needs to be adjusted, it needs to be redesigned from the design stage, resulting in long application service splitting time and high splitting difficulty; and the HPA algorithm scales up and down the entire application as a whole. When a single application interface experiences a traffic surge, other interfaces that do not experience a traffic surge will also scale up, resulting in resource waste and failing to solve the problem of resource contention between interfaces. Based on this, the service deployment methods of some embodiments of this disclosure can first perform interface tracking on each application interface in the application interface set corresponding to the target application to generate interface tracking data, obtaining an interface tracking dataset. Here, the interface tracking data is data obtained by monitoring the application interfaces, which facilitates the subsequent dynamic splitting of the target application based on the interface tracking data. Secondly, based on the preset service splitting configuration information, traffic statistics are performed on the aforementioned interface tracking dataset to obtain a traffic statistics information set. This traffic statistics information set helps determine the performance of the application interfaces, thus determining whether to dynamically split the target application. Then, based on the traffic statistics information set and the preset service splitting configuration information, the target application is dynamically split to obtain an application service information set and a service interface set. Here, the preset service splitting configuration information and traffic statistics information set allow for flexible splitting of the target application, enabling the binding and unbinding of application interfaces. Furthermore, if the preset service splitting configuration information pertains to a single application interface, it allows for scaling up or down that single application interface, reducing resource waste during scaling. Finally, the preset service splitting configuration information, the application service information set, and the service interface set are sent to the service deployment end for dynamic deployment. This enables automatic and flexible deployment of the application service information set and service interface set, improving deployment efficiency. Therefore, this service deployment method can monitor the load of application interfaces in real time by adding interface tracking points, and traffic statistics can fully understand the load on application interfaces or target applications, so as to perform targeted dynamic splitting based on the preset service splitting configuration information.Due to the different splitting conditions in the preset service splitting configuration information, flexible splitting of application interfaces or target applications can be achieved. This enables scaling up or down for a single application interface after splitting, without needing to scale up or down the entire target application. This reduces resource waste and improves the accuracy of dynamic splitting. Furthermore, the deployment of application services and application interfaces after splitting using the preset service splitting configuration information can improve deployment efficiency. Attached Figure Description

[0030] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and elements are not necessarily drawn to scale.

[0031] Figure 1 This is a schematic diagram of an application scenario of a service deployment method according to some embodiments of the present disclosure;

[0032] Figure 2 This is a flowchart of some embodiments of the service deployment method according to this disclosure;

[0033] Figure 3 These are flowcharts of other embodiments of the service deployment method according to this disclosure;

[0034] Figure 4 These are schematic diagrams illustrating the structure of some embodiments of the service deployment apparatus according to this disclosure;

[0035] Figure 5 This is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. Detailed Implementation

[0036] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0037] It should also be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings. Unless otherwise specified, the embodiments and features described in this disclosure can be combined with each other.

[0038] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0039] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0040] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0041] This disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0042] Figure 1 This is a schematic diagram of an application scenario of a service deployment method according to some embodiments of the present disclosure.

[0043] exist Figure 1 In this application scenario, electronic device 101 can first perform interface tracking on each application interface in the application interface set 103 corresponding to the target application 102 to generate interface tracking data, resulting in an interface tracking dataset 104. In this application scenario, the application interface set 103 may include: application interface A1031, application interface B1032, and application interface C1033. The interface tracking dataset 104 may include: interface tracking data 1041, interface tracking data 1042, and interface tracking data 1043. Next, according to the preset service splitting configuration information 105, traffic statistics are performed on the interface tracking dataset 104 to obtain a traffic statistics information set 106. Then, according to the traffic statistics information set 106 and the preset service splitting configuration information 105, the target application 102 is dynamically split to obtain an application service information set 107 and a service interface set 108. In this application scenario, the application service information set may include: application service information A1071 and application service information B1072. Finally, the aforementioned preset service split configuration information 105, the aforementioned application service information set 107, and the aforementioned service interface set 108 are sent to the service deployment terminal 109 for dynamic deployment by the service deployment terminal 109.

[0044] It should be noted that the aforementioned electronic device 101 can be either hardware or software. When the electronic device is hardware, it can be implemented as a distributed cluster consisting of multiple servers or terminal devices, or as a single server or a single terminal device. When the electronic device is software, it can be installed in the hardware devices listed above. It can be implemented as, for example, multiple software programs or software modules used to provide distributed services, or as a single software program or software module. No specific limitations are made here.

[0045] It should be understood that Figure 1The number of electronic devices shown is merely illustrative. Any number of electronic devices can be used depending on the implementation requirements.

[0046] Continue to refer to Figure 2 The diagram illustrates a flow 200 of some embodiments of a service deployment method according to the present disclosure. This service deployment method includes the following steps:

[0047] Step 201: Perform interface tracking for each application interface in the application interface set corresponding to the target application to generate interface tracking data and obtain the interface tracking dataset.

[0048] In some embodiments, the entity executing the above service deployment method (e.g.) Figure 1 The electronic device 101 shown can perform interface tracking on each application interface in the application interface set corresponding to the target application to generate interface tracking data and obtain an interface tracking dataset. The target application can be an application awaiting splitting. The application interfaces in the application interface set can be APIs (Application Programming Interfaces) for data exchange and service calls. The interface tracking data can be data collected at the entry and exit points of the application interface, showing the number of requests received by the application interface within a preset time period. The preset time period can be a pre-defined time interval. For example, the preset time period can be 1 second. The interface tracking data can be {"point": "common-server.***.NameService", "inTime": 17***92, "outTime": 17***92, "app": "common-service"}. "point" represents the application interface identifier. "common-server.***.NameService" represents the path of the application interface. "inTime" represents the timestamp of the request entering the application interface. "outTime" represents the timestamp of the request completing and leaving the application interface. "app" represents the name of the target application. The above-mentioned common-service refers to a specific application process.

[0049] As an example, the aforementioned execution entity can use a visual event tracking method to perform event tracking on each application interface in the application interface set corresponding to the target application, so as to generate event tracking data and obtain an event tracking dataset.

[0050] In some optional implementations of certain embodiments, the above-mentioned process of adding interface tracking points to each application interface in the application interface set corresponding to the target application to generate interface tracking point data and obtain an interface tracking point dataset may include the following steps:

[0051] The first step, in response to the detection that the target application has started successfully, is to load an application agent on the application virtual machine corresponding to the target application. The application virtual machine can be a virtual environment containing the resources required for the target application to start and run. The application agent can be a program used to monitor and modify the target application.

[0052] As an example, the aforementioned execution entity can utilize Java probe technology to load an application agent on the application virtual machine corresponding to the target application in response to the detection that the target application has started successfully.

[0053] The second step involves executing the target function in the application agent upon detecting successful application virtual machine startup. This function performs interface tracking for each application interface in the application interface set, resulting in an interface tracking dataset. The target function can be a function used to initialize the application agent. For example, the target function could be the `agentmain` function.

[0054] As an example, the aforementioned execution entity can, in response to the detection that the application virtual machine has started successfully, use the byteBuddy (Java bytecode manipulation library) tool to execute the target function in the aforementioned application proxy to perform interface tracking for each application interface in the aforementioned application interface set, thereby obtaining an interface tracking dataset.

[0055] Step 202: Based on the preset service splitting configuration information, perform traffic statistics on the above interface data set to obtain a traffic statistics information set.

[0056] In some embodiments, the execution entity can perform traffic statistics on the interface data set based on preset service splitting configuration information to obtain a traffic statistics information set. The preset service splitting configuration information can be user-defined configuration information that splits the target application into multiple services. The traffic statistics information in the traffic statistics information set can characterize the performance of the application interface or the target application. The traffic statistics information can include: statistical time period, application interface name or target application name, call volume metric, and TP (Top Percentile) performance metric. The call volume metric can be the number of requests made by the application interface or the target application within the statistical time period. The TP performance metric can characterize the time consumed by the application interface or the target application in processing the requests within the statistical time period, and is sorted in ascending order. The TP performance metric can include: TP50, TP90, TP99, and TP999. For example, the traffic statistics above could be {"app": "com***ver", "interfaceName": "com.***.NameService", "beginDate": 17***92, "endDate": 17***892, "TPS": 1000, "TP90": 50, "TP99": 60, "TP999": 100}. Here, "app" represents the identifier of the target application. "com***ver" can represent the specific name of the target application. "interfaceName" can represent the identifier of the application interface. "com.***.NameService" can represent the name of the specific application interface. "beginDate" can represent the start time of the statistics. "endDate" can represent the end time of the statistics. "TPS" (Transactions Per Second) can represent the number of requests processed per second by the application interface. "TP90" can indicate that within the above statistical period, 90% of the requests were processed within 50 milliseconds. The aforementioned TP99 indicates that within the aforementioned statistical time period, 99% of the request information was processed within 60 milliseconds. The aforementioned TP999 indicates that within the aforementioned statistical time period, 99.9% of the request information was processed within 100 milliseconds.

[0057] As an example, the aforementioned execution entity can first extract the statistical time from the preset service split configuration information to obtain the target statistical time. Then, using the target statistical time, it can perform traffic statistics on the aforementioned interface tracking dataset to obtain a traffic statistics information set.

[0058] In some optional implementations of certain embodiments, the above-mentioned method of performing traffic statistics on the interface data set based on preset service splitting configuration information to obtain a traffic statistics information set may include the following steps:

[0059] The first step, in response to determining that the aforementioned preset service splitting configuration information is application interface splitting information, is to determine the interface tracking data corresponding to the aforementioned preset service splitting configuration information as the target interface tracking data. The aforementioned application interface splitting information can be preset service splitting configuration information for application interfaces.

[0060] The second step involves performing traffic statistics on the target interface's event tracking data based on the statistical time period included in the aforementioned preset service splitting configuration information, thereby obtaining traffic statistics information. The aforementioned statistical time period can be the time period during which request information is processed from the target interface's event tracking data. The aforementioned traffic statistics information can be information obtained from statistics within the aforementioned application interface's statistical time period.

[0061] Optionally, the above-mentioned traffic statistics data set obtained by performing traffic statistics on the interface tracking dataset based on the preset service split configuration information may include the following steps:

[0062] The first step, in response to determining that the aforementioned preset service splitting configuration information is application splitting information, is to determine at least one interface tracking data set corresponding to the aforementioned target application. The aforementioned application splitting information can be preset service splitting configuration information for the target application. The interface tracking data in the aforementioned at least one interface tracking data set can be tracking data that satisfies the aforementioned preset service splitting configuration information. In practice, the executing entity can first, in response to determining that the aforementioned preset service splitting configuration information is application splitting information, extract application interfaces from the aforementioned preset service splitting configuration information to obtain the target application interface set. Then, it can determine at least one interface tracking data set corresponding to the aforementioned target application interface set.

[0063] The second step involves performing traffic statistics on the at least one interface tracking data set based on the statistical time period included in the aforementioned preset service splitting configuration information, thereby obtaining traffic statistics information. This traffic statistics information can be data obtained from statistics within the statistical time period for the target application. In practice, the executing entity can first summarize the traffic of each interface tracking data set in the at least one interface tracking data set over the statistical time period, obtaining at least one traffic summary information set. Then, traffic statistics are performed on the at least one traffic summary to obtain traffic statistics information.

[0064] Step 203: Based on the above traffic statistics information set and the above preset service splitting configuration information, the above target application is dynamically split to obtain the application service information set and service interface set.

[0065] In some embodiments, the execution entity can dynamically split the target application based on the traffic statistics information set and the preset service splitting configuration information to obtain an application service information set and a service interface set. The application services in the application service information set can be applications that are independently split from the target application and can perform specific business operations or functions. The service interfaces in the service interface set can be application interfaces corresponding to the application service information. For example, the target application can be an application that handles business 1 and business 2. Because business 2 handles a large number of business operations and has a heavy workload, business 2 is independently split from the target application to obtain service 1 and service 2. Service 1 corresponds to the service that handles business 1. Service 2 corresponds to the service that handles business 2.

[0066] As an example, the aforementioned execution entity can first determine the traffic statistics information in the aforementioned traffic statistics information set that satisfies the aforementioned preset service splitting configuration information, and use this as the target traffic statistics information. Then, using the aforementioned preset service splitting configuration information, the dependencies of the application interfaces corresponding to the target traffic statistics information are determined. These dependencies can characterize the independence and integrability of the application interfaces. These dependencies may include, but are not limited to, at least one of the following: data dependency, communication dependency, and version dependency. Finally, using the aforementioned preset service splitting configuration information and dependencies, the application interfaces corresponding to the target traffic statistics information are vertically split to obtain an application service information set and a service interface set.

[0067] In some optional implementations of certain embodiments, the dynamic splitting of the target application based on the traffic statistics information set and the preset service splitting configuration information to obtain the application service information set and service interface set may include the following steps:

[0068] The first step, in response to determining that the aforementioned preset service splitting configuration information is application interface splitting information, involves separating the process corresponding to at least one application interface from the target application, resulting in a split service information set. The split service information in this set can be information about an application that can perform specific business or functions, extracted from the target application. For example, the preset service splitting configuration information could be: when the TPS of application interface 1 in the target application is greater than or equal to 10000, the configuration information for splitting application interface 1 from the target application as an independent service, and only scaling application interface 1. In this case, the split application could be the functional scope and code corresponding to application interface 1 extracted from the target application as a separate service.

[0069] The second step involves scaling up or down the split service set corresponding to the aforementioned pre-defined service splitting configuration information to obtain the application service information set. The application service information in this set can be obtained by adding or removing service instances of the split application.

[0070] The third step is to take the application interface group corresponding to each application service information in the above application service information set as the service interface, and obtain the service interface set.

[0071] Optionally, the above-mentioned dynamic splitting of the target application based on the traffic statistics information set and the preset service splitting configuration information to obtain the application service information set and service interface set may include the following steps:

[0072] The first step is to determine that the above-mentioned preset service splitting configuration information is application splitting information, and to perform scaling up and down processing on the process corresponding to at least one target application interface according to the above-mentioned preset service splitting configuration information, so as to obtain the scaled up and down application interface set as the service interface set, wherein the above-mentioned at least one target application interface is multiple interfaces corresponding to the above-mentioned preset service splitting configuration information.

[0073] The second step is to identify the target applications mentioned above as target service information, which will be used as the application service information set.

[0074] Step 204: Send the above-mentioned preset service split configuration information, the above-mentioned application service information set, and the above-mentioned service interface set to the service deployment end for dynamic deployment.

[0075] In some embodiments, the execution entity may send the preset service splitting configuration information, the application service information set, and the service interface set to the service deployment end for dynamic deployment. The service deployment end may be a server used to deploy the application service set and service interface set corresponding to the application service information set.

[0076] The above service deployment is dynamically deployed through the following steps:

[0077] The first step is to generate a container deployment image set based on the received preset service splitting configuration information, application service information set, and service interface set. The container deployment images in this set can be independent software packages containing the content required for running the application service corresponding to the application service information. This required content may include, but is not limited to, at least one of the following: code, runtime environment, system libraries, and configuration files.

[0078] As an example, the service deployment end can determine the service code, service dependencies, and container environment of each application service in the application service information set based on the preset service split configuration information, thus obtaining a service code set, a service dependency set, and a container environment set. The service dependencies can be third-party libraries and software packages required for the application service to run. The container environment can be the runtime environment for the coding language image and environment variables required by the application service. Then, using Docker technology, the service code set, service dependency set, and container environment set are packaged accordingly to obtain a container deployment image set.

[0079] The second step is to deploy the above application service information set and the above service interface set based on the container deployment image set.

[0080] As an example, the service deployment end can integrate the container deployment image into the Kubernetes (K8S) system by calling the OSS (Object Storage Service) SDK (Software Development Kit). Then, it can call the K8S SDK to deploy the application service information set and the service interface set.

[0081] The above embodiments of this disclosure have the following beneficial effects: the service deployment methods of some embodiments of this disclosure can improve the flexibility and efficiency of target application splitting, and the splitting is based on application interfaces, allowing for the splitting of individual interfaces, which can reduce resource waste. Specifically, the reasons for the long splitting time, high splitting difficulty, and resource waste of related application services, and the inability to solve the problem of resource contention between interfaces, are as follows: since static splitting is determined in the architecture design stage and cannot be dynamically adjusted in subsequent applications, if the architecture needs to be adjusted, it needs to be redesigned from the design stage, resulting in long application service splitting time and high splitting difficulty; and the HPA algorithm scales up and down the entire application as a whole. When a single application interface experiences a traffic surge, other interfaces that do not experience a traffic surge will also scale up, resulting in resource waste and failing to solve the problem of resource contention between interfaces. Based on this, the service deployment methods of some embodiments of this disclosure can first perform interface tracking on each application interface in the application interface set corresponding to the target application to generate interface tracking data, obtaining an interface tracking dataset. Here, the interface tracking data is data obtained by monitoring the application interfaces, which facilitates the subsequent dynamic splitting of the target application based on the interface tracking data. Secondly, based on the preset service splitting configuration information, traffic statistics are performed on the aforementioned interface tracking dataset to obtain a traffic statistics information set. This traffic statistics information set helps determine the performance of the application interfaces, thus determining whether to dynamically split the target application. Then, based on the traffic statistics information set and the preset service splitting configuration information, the target application is dynamically split to obtain an application service information set and a service interface set. Here, the preset service splitting configuration information and traffic statistics information set allow for flexible splitting of the target application, enabling the binding and unbinding of application interfaces. Furthermore, if the preset service splitting configuration information pertains to a single application interface, it allows for scaling up or down that single application interface, reducing resource waste during scaling. Finally, the preset service splitting configuration information, the application service information set, and the service interface set are sent to the service deployment end for dynamic deployment. This enables automatic and flexible deployment of the application service information set and service interface set, improving deployment efficiency. Therefore, this service deployment method can monitor the load of application interfaces in real time by adding interface tracking points, and traffic statistics can fully understand the load on application interfaces or target applications, so as to perform targeted dynamic splitting based on the preset service splitting configuration information.Due to the different splitting conditions in the preset service splitting configuration information, flexible splitting of application interfaces or target applications can be achieved. This enables scaling up or down for a single application interface after splitting, without needing to scale up or down the entire target application. This reduces resource waste and improves the accuracy of dynamic splitting. Furthermore, the deployment of application services and application interfaces after splitting using the preset service splitting configuration information can improve deployment efficiency.

[0082] Further reference Figure 3 The following diagram illustrates a flow 300 of another embodiment of a service deployment method according to the present disclosure. This service deployment method includes the following steps:

[0083] Step 301: Register the application interface set corresponding to the target application and the target application.

[0084] In some embodiments, the executing entity (e.g. Figure 1 The electronic device shown can register the application interface set corresponding to the target application and the aforementioned target application.

[0085] As an example, the aforementioned execution entity can utilize a service discovery framework and interface gateway to register the application interface set corresponding to the target application and the target application itself. The service discovery framework could be the Consul framework.

[0086] In some optional implementations of certain embodiments, the registration of the application interface set corresponding to the target application and the target application may include the following steps:

[0087] The first step is to add the interface path set corresponding to the above application interface set and the process identifier corresponding to the target application to the environment configuration file, resulting in the added environment configuration file. This environment configuration file can be a file configuring the environment of the application proxy. For example, it can be a predefined file configuring the runtime environment of the target application. The interface paths represent the location of the application interfaces within the target process. The process identifier represents the unique identifier of the target process.

[0088] The second step involves detecting that the application proxy corresponding to the target application has started successfully. Based on the added environment configuration file, the aforementioned set of interface paths and the application representation are registered with the service processing end. This service processing end can be a server that registers application services and application interfaces. For example, it could be Zookeeper (a distributed application coordination service software).

[0089] As an example, the aforementioned execution entity can, in response to detecting that the application agent corresponding to the target application has started successfully, control the application agent to perform a file scan on the added environment configuration file and obtain the scan results. Then, using an HTTP (Hypertext Transfer Protocol) request, it registers the process identifier of the target application and the set of interface paths corresponding to the application interface, including the scan results, to the service governance end.

[0090] In some optional implementations of certain embodiments, the registration of the application interface set corresponding to the target application and the target application may include the following steps:

[0091] The first step is to determine the service registration file corresponding to the aforementioned service processing terminal. This service registration file can be a file recorded by the service processing terminal containing the process name and interface path registered with it.

[0092] The second step is to add the interface path set corresponding to the above application interface set and the application identifier of the above target application to the above service registration file in order to register the above application interface set and the above target application.

[0093] Step 302: In response to the successful registration of the application interface set and the target application, interface tracking is performed on each application interface in the application interface set to generate interface tracking data and obtain the interface tracking dataset.

[0094] Step 303: Based on the preset service splitting configuration information, perform traffic statistics on the above interface tracking dataset to obtain a traffic statistics information set.

[0095] Step 304: Based on the above traffic statistics information set and the above preset service splitting configuration information, the above target application is dynamically split to obtain the application service information set and service interface set.

[0096] Step 305: Send the above-mentioned preset service split configuration information, the above-mentioned application service information set, and the above-mentioned service interface set to the service deployment end for dynamic deployment.

[0097] In some embodiments, the specific implementation of steps 302-305 and the resulting technical effects can be found in [reference needed]. Figure 2 Steps 201-204 in the corresponding embodiments will not be repeated here.

[0098] from Figure 3 It can be seen from this that, with Figure 2 Compared to the description of some corresponding embodiments, Figure 3In some corresponding embodiments, the service deployment method process 300 emphasizes the specific steps of performing interface tracking for each application interface in the application interface set corresponding to the target application to generate interface tracking data and obtain the interface tracking dataset. Therefore, the solutions described in these embodiments, by registering only the application interfaces and the target application before splitting the target application, and dynamically splitting based on the subsequent operation of the application interfaces and target services, eliminate the need to consider the service-oriented issues after the target application is split, reducing the workload of service splitting the target application, enabling rapid and agile development of the target application, and improving the efficiency of service splitting.

[0099] Further reference Figure 4 As an implementation of the methods shown in the above figures, this disclosure provides some embodiments of a service deployment apparatus, which are similar to... Figure 2 Corresponding to the method embodiments shown, the device can be specifically applied to various electronic devices.

[0100] like Figure 4 As shown, a service deployment device 400 includes: an interface tracking unit 401, a traffic statistics unit 402, a dynamic splitting unit 403, and a sending unit 404. The interface tracking unit 401 is configured to: perform interface tracking on each application interface in the application interface set corresponding to the target application to generate interface tracking data, obtaining an interface tracking dataset. The traffic statistics unit 402 is configured to: perform traffic statistics on the interface tracking dataset according to preset service splitting configuration information, obtaining a traffic statistics information set. The dynamic splitting unit 403 is configured to: perform dynamic splitting processing on the target application according to the traffic statistics information set and the preset service splitting configuration information, obtaining an application service information set and a service interface set. The sending unit 404 is configured to send the preset service splitting configuration information, the application service information set, and the service interface set to the service deployment end for dynamic deployment.

[0101] In some optional implementations of some embodiments, the traffic statistics unit 402 may be further configured to: in response to determining that the preset service splitting configuration information is application interface splitting information, determine the interface tracking data corresponding to the preset service splitting configuration information as target interface tracking data; and perform traffic statistics on the target interface tracking data according to the statistical time period included in the preset service splitting configuration information to obtain traffic statistics information.

[0102] In some optional implementations of some embodiments, the traffic statistics unit 402 may be further configured to: in response to determining that the preset service splitting configuration information is application splitting information, determine at least one interface tracking data set corresponding to the target application; and perform traffic statistics on the at least one interface tracking data set according to the statistical time period included in the preset service splitting configuration information to obtain traffic statistics information.

[0103] In some optional implementations of certain embodiments, the dynamic splitting unit 403 may be further configured to: in response to determining that the preset service splitting configuration information is application interface splitting information, split the process corresponding to at least one application interface corresponding to the preset service splitting configuration information from the target application to obtain a split service information set; perform scaling processing on the service set corresponding to the split service information set according to the preset service splitting configuration information to obtain an application service information set; and take the application interface group corresponding to each application service information in the application service information set as a service interface to obtain a service interface set.

[0104] In some optional implementations of some embodiments, the dynamic splitting unit 403 may be further configured to: in response to determining that the preset service splitting configuration information is application splitting information, perform scaling up or down processing on the process corresponding to at least one application interface according to the preset service splitting configuration information to obtain a scaled-down application interface set as a service interface set, wherein the at least one application interface is corresponding to the preset service splitting configuration information; and determine the target application as target service information as an application service information set.

[0105] In some optional implementations of some embodiments, the interface tracking unit can be configured to: register the application interface set corresponding to the target application and the target application; in response to determining that the application interface set and the target application are successfully registered, perform interface tracking on each application interface in the application interface set corresponding to the target application to generate interface tracking data and obtain an interface tracking dataset.

[0106] In some optional implementations of some embodiments, the interface tracking unit 401 may be further configured to: add the interface path set corresponding to the application interface set and the application identifier of the target application to the environment configuration file to obtain the added environment configuration file; in response to detecting that the application agent corresponding to the target application has started successfully, register the interface path set and the application identifier to the service processing end according to the added environment configuration file.

[0107] In some optional implementations of some embodiments, the interface tracking unit 401 may be further configured to: determine the service registration file corresponding to the service processing terminal; add the interface path set corresponding to the application interface set and the application identifier of the target application to the service registration file to register the application interface set and the target application.

[0108] In some optional implementations of some embodiments, the interface tracking unit 401 may be further configured to: in response to detecting that the target application has started successfully, load an application agent on the application virtual machine corresponding to the target application; in response to detecting that the application virtual machine has started successfully, execute the target function in the application agent to perform interface tracking on each application interface in the application interface set to obtain an interface tracking dataset.

[0109] It is understandable that the units described in the device 400 are related to the reference. Figure 2 The steps in the described method correspond accordingly. Therefore, the operations, features, and beneficial effects described above for the method also apply to device 400 and the units contained therein, and will not be repeated here.

[0110] The following is for reference. Figure 5 It illustrates electronic devices suitable for implementing some embodiments of this disclosure (e.g., Figure 1 A schematic diagram of the structure of electronic device 101)500. Figure 5 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments of this disclosure.

[0111] like Figure 5 As shown, the electronic device 500 may include a processing unit (e.g., a central processing unit, a graphics processor, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 into a random access memory (RAM) 503. The RAM 503 also stores various programs and data required for the operation of the electronic device 500. The processing unit 501, ROM 502, and RAM 503 are interconnected via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0112] Typically, the following devices can be connected to I / O interface 505: input devices 506 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 507 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 508 including, for example, magnetic tapes, hard disks, etc.; and communication devices 509. Communication device 509 allows electronic device 500 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 5 An electronic device 500 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively. Figure 5 Each box shown can represent a device or multiple devices as needed.

[0113] In particular, according to some embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, some embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 509, or installed from storage device 508, or installed from ROM 502. When the computer program is executed by processing device 501, it performs the functions defined in the methods of some embodiments of this disclosure.

[0114] It should be noted that, in some embodiments of this disclosure, the computer-readable medium described above may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In some embodiments of this disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In some embodiments of this disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0115] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0116] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device. The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to: perform interface tracking on each application interface in the application interface set corresponding to the target application to generate interface tracking data, obtaining an interface tracking dataset; perform traffic statistics on the interface tracking dataset according to preset service splitting configuration information to obtain a traffic statistics information set; perform dynamic splitting processing on the target application according to the traffic statistics information set and the preset service splitting configuration information to obtain an application service information set and a service interface set; and send the preset service splitting configuration information, the application service information set, and the service interface set to the service deployment end for dynamic deployment.

[0117] Computer program code for performing operations of some embodiments of this disclosure can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0118] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0119] The units described in some embodiments of this disclosure can be implemented in software or hardware. The described units can also be housed in a processor; for example, a processor may be described as including an interface tracking unit, a traffic statistics unit, a dynamic splitting unit, and a sending unit. The names of these units do not necessarily limit the specific unit itself; for example, an interface tracking unit may also be described as "a unit that performs interface tracking on each application interface in a set of application interfaces corresponding to a target application to generate interface tracking data and obtain an interface tracking dataset."

[0120] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0121] Some embodiments of this disclosure also provide a computer program product, including a computer program that, when executed by a processor, implements any of the service deployment methods described above.

[0122] The above description is merely a selection of preferred embodiments of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in the embodiments of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described inventive concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features with similar functions disclosed in the embodiments of this disclosure.

Claims

1. A service deployment method, comprising: For each application interface in the application interface set corresponding to the target application, interface tracking points are added to generate interface tracking point data, resulting in an interface tracking point dataset. Based on the preset service splitting configuration information, traffic statistics are performed on the interface tracking dataset to obtain a traffic statistics information set. Based on the traffic statistics information set and the preset service splitting configuration information, the target application is dynamically split to obtain an application service information set and a service interface set. The preset service split configuration information, the application service information set, and the service interface set are sent to the service deployment end for dynamic deployment.

2. The method according to claim 1, wherein, The step involves performing traffic statistics on the interface tracking dataset based on preset service splitting configuration information to obtain a traffic statistics information set, including: In response to determining that the preset service splitting configuration information is application interface splitting information, the interface tracking data corresponding to the preset service splitting configuration information is determined as the target interface tracking data; Based on the statistical time period included in the preset service split configuration information, traffic statistics are performed on the target interface data points to obtain traffic statistics information.

3. The method according to claim 1, wherein, The step involves performing traffic statistics on the interface tracking dataset based on preset service splitting configuration information to obtain a traffic statistics information set, including: In response to determining that the preset service splitting configuration information is application splitting information, at least one interface data set corresponding to the target application is determined. Based on the statistical time period included in the preset service split configuration information, traffic statistics are performed on the at least one interface data set to obtain traffic statistics information.

4. The method according to claim 1, wherein, The step of dynamically splitting the target application based on the traffic statistics information set and the preset service splitting configuration information to obtain an application service information set and a service interface set includes: In response to determining that the preset service splitting configuration information is application interface splitting information, the process corresponding to at least one application interface corresponding to the preset service splitting configuration information is separated from the target application to obtain a split service information set. Based on the preset service splitting configuration information, the service set corresponding to the split service information set is expanded or shrunk to obtain the application service information set. The application interface group corresponding to each application service information in the application service information set is taken as the service interface to obtain the service interface set.

5. The method according to claim 1, wherein, The step of dynamically splitting the target application based on the traffic statistics information set and the preset service splitting configuration information to obtain an application service information set and a service interface set includes: In response to determining that the preset service splitting configuration information is application splitting information, scaling up or down the process corresponding to at least one target application interface is performed according to the preset service splitting configuration information to obtain a scaled-down application interface set as a service interface set, wherein the at least one target application interface is the one corresponding to the preset service splitting configuration information. The target application is identified as the target service information, which is then used as the application service information set.

6. The method according to claim 1, wherein performing interface tracking on each application interface in the application interface set corresponding to the target application to generate interface tracking data and obtain an interface tracking dataset includes: Register the application interface set corresponding to the target application and the target application itself; In response to the successful registration of the application interface set and the target application, interface tracking is performed on each application interface in the application interface set to generate interface tracking data, thus obtaining an interface tracking dataset.

7. The method according to claim 6, wherein, The registration of the application interface set corresponding to the target application and the target application includes: Add the interface path set corresponding to the application interface set and the application identifier of the target application to the environment configuration file to obtain the environment configuration file after addition; In response to the detection that the application agent corresponding to the target application has started successfully, the interface path set and the application identifier are registered to the service processing end according to the added environment configuration file.

8. The method according to claim 6, wherein, The registration of the application interface set corresponding to the target application and the target application includes: Determine the service registration file corresponding to the service processing terminal; The interface path set corresponding to the application interface set and the application identifier of the target application are added to the service registration file to register the application interface set and the target application.

9. The method according to claim 1, wherein, The step of performing interface tracking on each application interface in the application interface set corresponding to the target application to generate interface tracking data, resulting in an interface tracking dataset, includes: In response to the detection that the target application has started successfully, an application agent is loaded on the application virtual machine corresponding to the target application. In response to the detection that the application virtual machine has started successfully, the target function in the application agent is executed to perform interface tracking for each application interface in the application interface set, thereby obtaining an interface tracking dataset.

10. A service deployment apparatus, comprising: The interface tracking unit is configured to track each application interface in the application interface set corresponding to the target application to generate interface tracking data and obtain the interface tracking dataset. The traffic statistics unit is configured to perform traffic statistics on the interface tracking dataset according to preset service splitting configuration information to obtain a traffic statistics information set. The dynamic splitting unit is configured to dynamically split the target application based on the traffic statistics information set and the preset service splitting configuration information to obtain an application service information set and a service interface set. The sending unit is configured to send the preset service splitting configuration information, the application service information set, and the service interface set to the service deployment end for dynamic deployment.

11. An electronic device, comprising: One or more processors; Storage device, on which one or more programs are stored, When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-9.

12. A computer-readable medium having a computer program stored thereon, wherein, When the program is executed by the processor, it implements the method as described in any one of claims 1-9.

13. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1-9.

Images