Service deployment and routing method and device based on cloud native platform

Abstract

The invention discloses a service deployment and routing method and device based on a cloud native platform. The method is characterized by comprising the following steps: receiving packet routing information and routing mark information sent by a server; processing a routing selection mark combination of a service consumer, and reading a calling area and calling environment information of the service consumer; wherein the routing selection mark combination comprises grouping routing information and a routing selection mark combination; filtering the routing mark information based on the routing selection mark combination, the calling area and the calling environment information, and determining a routing grouping list; and carrying out service calling for the service consumer based on the routing grouping list. Routing marking and grouping improve flexibility, accuracy and intelligence of service calling, efficient and accurate routing selection can be ensured in a complex service scene through accurate routing selection of the label, calling efficiency is improved, delay is reduced, and stability and adaptivity of a system are effectively enhanced.

Description

Technical Field

[0001] The present invention relates to the field of cloud platform technology, and in particular to a service deployment and routing method and device based on a cloud native platform. Background Art

[0002] With the rapid development of cloud computing technology, cloud-native architecture has become a key model for modern application development. Cloud-native architectures, through technologies such as containerization, microservices, continuous integration, and continuous delivery, have significantly improved the efficiency of application development, deployment, and operation. However, within a microservices architecture, efficient service discovery and invocation pose a significant challenge. Existing technologies typically employ service registration and discovery mechanisms, such as Consul and Eureka. These mechanisms primarily record service information in a service registry and return the address of a service instance upon consumer request. However, with the increasing number of microservices and the increasing complexity of service invocation, traditional service discovery mechanisms have become limited in flexibility and accuracy. They struggle to reuse the routing capabilities of cloud platforms and cannot meet the multi-dimensional and multi-label service invocation requirements. Summary of the Invention

[0003] The present invention provides a service deployment and routing method and device based on a cloud native platform to solve the technical problem that the cloud native platform in the prior art cannot establish a flexible routing selection mechanism and provide service call performance.

[0004] According to one aspect of the present invention, a service deployment and routing method based on a cloud native platform is provided, which is applied to a client; the method comprises:

[0005] Receive packet routing information and routing tag information sent by the server;

[0006] Processing the routing tag combination of the service consumer and reading the calling area and calling environment information of the service consumer; wherein the routing tag combination includes packet routing information and the routing tag combination;

[0007] Filtering the routing tag information based on the routing tag combination, the calling area, and the calling environment information to determine a routing group list;

[0008] A service call is made for the service consumer based on the routing group list.

[0009] According to another aspect of the present invention, a service deployment and routing method based on a cloud native platform is provided, which is applied to a server; the method comprises:

[0010] receiving at least one deployment group application of a service application deployed by a service provider on a cloud native platform and group routing information of the deployment group application;

[0011] For each of the deployment group applications, setting routing tag information for the deployment group application based on a preset tagging method;

[0012] The group routing information and the routing tag information of each of the deployed group applications are pushed to the client.

[0013] According to another aspect of the present invention, a service deployment and routing device based on a cloud native platform is provided, which is deployed on a client and includes:

[0014] The communication module is used to receive the packet routing information and routing mark information sent by the server;

[0015] a processing module, configured to process a routing tag combination of a service consumer and read the calling region and calling environment information of the service consumer; wherein the routing tag combination includes packet routing information and a routing tag combination;

[0016] A grouping module, configured to filter the routing tag information based on the routing tag combination, the calling area, and the calling environment information, and determine a routing grouping list;

[0017] A calling module is used to call a service for the service consumer based on the routing group list.

[0018] According to another aspect of the present invention, a service deployment and routing device based on a cloud native platform is provided, which is deployed on a server side and includes:

[0019] a platform connection module, configured to receive at least one deployment group application of a service application deployed by a service provider on a cloud native platform and group routing information of the deployment group application;

[0020] a processing module, configured to set routing tag information for each of the deployment group applications based on a preset tagging method;

[0021] A push module is used to push the group routing information and the routing tag information of each deployed group application to the client.

[0022] The technical solution of the embodiment of the present invention receives the group routing information and routing tag information sent by the service end; processes the routing tag combination of the service consumer, and reads the calling area and calling environment information of the service consumer; improves the flexibility, standardization and intelligence of service calls through routing tags and grouping, and the client can provide routing support for consumers through multi-dimensional attributes; filters the routing tag information based on the routing tag combination, calling area and calling environment information, determines the routing group list, and through precise routing selection based on labels, can automatically match routes based on the business needs of the consumer and the tag information, thereby achieving precise and efficient service routing selection; and performs service calls for the service consumer based on the routing group list. The existing cloud native platform is unable to establish a flexible routing selection mechanism and provide technical problems for service call performance. Through precise routing selection based on labels, it is possible to ensure efficient and accurate routing selection in complex business scenarios, improve calling efficiency, reduce latency, and effectively enhance the stability and adaptability of the system.

[0023] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the present invention. Other features of the present invention will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0025] Figure 1 A schematic diagram of a typical deployment architecture of a cloud native platform provided by an embodiment of the present invention;

[0026] Figure 2 A flowchart of a service deployment and routing method based on a cloud native platform is provided for an embodiment of the present invention;

[0027] Figure 3 A flowchart of another service deployment and routing method based on a cloud native platform is provided for an embodiment of the present invention;

[0028] Figure 4 A flowchart of another service deployment and routing method based on a cloud native platform is provided for an embodiment of the present invention;

[0029] Figure 5 A flowchart of another service deployment and routing method based on a cloud native platform is provided for an embodiment of the present invention;

[0030] Figure 6 A schematic diagram of the structure of a service deployment and routing device based on a cloud native platform provided by an embodiment of the present invention;

[0031] Figure 7 A schematic diagram of the structure of another cloud-native platform-based service deployment and routing device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0032] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0033] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0034] Figure 1 A schematic diagram of a typical deployment architecture of a cloud native platform provided in an embodiment of the present invention is shown as follows: Figure 1 As shown: the client communicates with the server through the cloud native platform, the server is independently deployed from the cloud native platform, and is connected to the cloud native platform API (Application Programming Interface). The client is integrated into the corresponding application of the service consumer.

[0035] Optionally, in the present invention, a cloud native platform is an application platform built on cloud computing infrastructure that supports features such as automatic expansion, rapid deployment, and elastic scaling. Service applications are deployed on the cloud native platform to provide one or more achievable functions for service consumers. The service consumer can be an application that calls one or more transactions with a service provider (service application).

[0036] Optionally, in the present invention, the client can also be deployed in a service grid manner.

[0037] Optionally, when deploying a service application, a service application is split into multiple independently deployable deployment group applications. Each deployment group application can bind the corresponding container internal and external service routing information as its own group routing information in the cloud native platform. Through the group routing information, it can be connected to a deployment group application to call the service of the deployment group application.

[0038] Alternatively, a container is a lightweight virtualization technology used to package and deploy grouped applications and their dependencies in an independent environment. It is isolated from the host system and can run consistently across different environments.

[0039] Optionally, the routing information for external services within a container includes the container's external service address and the container's internal service address. The external service address is the address from which the containerized service can be accessed from external systems or users. It is typically exposed to the outside world by a load balancer or gateway, interacting with services provided by the deployed grouped applications within the container through a specific port or domain name. The internal service address is the network address used for communication between containers or between a container and internal systems, and is typically visible within a private network.

[0040] Optionally, the cloud native platform API can be an API interface provided by the container orchestration tool corresponding to the cloud native platform, which is a programming interface for interacting with external systems or controlling tasks such as container lifecycle management and resource scheduling.

[0041] Figure 2 The present invention provides a flowchart of a service deployment and routing method based on a cloud native platform. This embodiment can be applied to a client to respond to the routing selection tag combination of the service consumer and push a service route that satisfies the routing selection tag combination to the service consumer. The method can be executed by a service deployment and routing device based on a cloud native platform. The service deployment and routing device based on a cloud native platform can be implemented in the form of hardware and / or software. The service deployment and routing device based on a cloud native platform can be configured in the client. Figure 2 As shown, the method includes:

[0042] S210: Receive packet routing information and routing tag information sent by the server.

[0043] The group routing information may be service routing information of a deployment group application of the cloud native platform, and the deployment group application of the cloud native platform can be called through the group routing information. It should be noted that in the present invention, the group routing information and the routing tag information are one-to-one corresponding information. Each deployment group application has corresponding group routing information and routing tag information. Based on the group routing information and routing tag information, a unique deployment group application can be determined and then called.

[0044] Optionally, the server sends the group routing information and routing mark information of each deployed group application to each client, and the client receives the group routing information and routing mark information of each deployed group application.

[0045] The routing tag information may be tag information for multiple dimensions of the group routing information of the deployment group application. It should be noted that the routing tag information is obtained by setting routing tags corresponding to each dimension for the deployment group application using multiple dimensions such as deployment area, deployment environment, application version, grayscale attributes, blue-green grouping, data unit, and cluster.

[0046] Optionally, when setting routing tags corresponding to each dimension, a first tag priority corresponding to each routing tag is also set. The first tag priority of a routing tag can indicate the importance of a routing tag in the routing tag information. For example, when the routing tags are deployment areas and application version numbers, the first tag priority of the deployment area is set higher than the first tag priority of the application version number. The server considers that the deployment area of ​​the deployment group application is more important than the version of the deployment group application.

[0047] Specifically, the client receives the group routing information and routing tag information of multiple deployment group applications pushed by the server.

[0048] S220: Process the routing tag combination of the service consumer, and read the calling area and calling environment information of the service consumer.

[0049] The routing tag combination can be a routing tag combination selected by the service consumer each time it calls a service application based on its own business needs and call priority. The client can use the routing tag combination to match at least one deployment group application required by the service consumer from multiple deployment group applications.

[0050] Optionally, the routing tag combination includes at least one routing tag and a second tag priority for each routing tag. The second tag priority may be a selection priority set by the service consumer for the routing tag, indicating that routing tags with higher second tag priorities are preferentially matched during the deployment group application matching process.

[0051] The calling area may be the geographical area where the service consumer initiates the service call; and the calling environment information may be the operating environment in which the service consumer is located.

[0052] Specifically, when the service consumer sends the routing tag combination to the client, since the client is configured in the service consumer, the client can obtain the calling area and calling environment information of the service consumer.

[0053] S230: Filter the routing tag information based on the routing tag combination, the calling area, and the calling environment information to determine a routing group list.

[0054] The routing group list may be a list of group routing information of deployed group applications that meet the service consumer's call requirements. It should be noted that the client sets a routing group list for the service consumer and makes service calls for the service consumer based on the group routing information recorded in the routing group list.

[0055] Optionally, after obtaining the routing selection tag combination of the service consumer, the client matches, filters and selects the routing tag information of the service consumer in all deployed group applications of the client based on the service consumer's calling area, calling environment information and routing selection tag combination to obtain a routing group list.

[0056] Specifically, the routing tag information is filtered based on the routing tag combination, the calling area, and the calling environment information to determine the routing group list.

[0057] Optionally, in another optional embodiment of the present invention, filtering the routing tag information based on the routing tag combination, the calling region, and the calling environment information to determine the routing group list includes:

[0058] filtering the routing tag information according to the calling area and the calling environment information to determine an optional grouping route;

[0059] The selectable packet routes are selected according to the routing tag combination to determine the routing group list.

[0060] The optional group routing can be a data list that records the group routing information and routing tag information of the deployment group applications that match the service consumer on the consumer side. It should be noted that the optional group routing is used to record the deployment group applications that match the service consumer's calling region and calling environment information, and record the application routing tag information and group routing information of each deployment group.

[0061] Optionally, before selecting a deployment group application for a service consumer, the service consumer's calling area and calling environment information are used as filtering conditions, and the routing tag information of the deployment group application is filtered in all the deployment group applications on the consumer side to obtain a matching deployment group application, and the group routing information and routing tag information of the deployment group application are recorded in the selectable group routing.

[0062] Optionally, in another optional embodiment of the present invention, if the consumer end cannot obtain the calling area and calling environment information of the service consumer, there is no need to filter the deployed group applications on the consumer end, and the group routing information and routing mark information of all deployed group applications are recorded in the selectable group routing.

[0063] Optionally, after obtaining the optional group routing of the service consumer, based on the routing selection tag combination as the matching condition, the routing tag information in the optional group routing is matched in sequence to determine whether all routing tags of the routing selection tag combination exist in one routing tag information at the same time. If so, the group routing information corresponding to the routing tag information is written into the routing group list; if not, the judgment process is repeated for the next routing tag information until all the routing tag information in the optional group routing is matched once to obtain the routing group list.

[0064] Specifically, the routing tag information is filtered according to the calling area and calling environment information to determine the selectable group routes; the selectable group routes are routed according to the routing selection tag combination to determine the routing group list.

[0065] S240: Perform a service call for the service consumer based on the routing group list.

[0066] Specifically, after obtaining the routing group list matching the service consumer, group routing information is selected for the service consumer based on the group routing information in the routing group list, and the deployment group application corresponding to the group routing information is called to make a service call for the service consumer.

[0067] The technical solution of the embodiment of the present invention receives the group routing information and routing tag information sent by the service end; processes the routing tag combination of the service consumer, and reads the calling area and calling environment information of the service consumer; improves the flexibility, standardization and intelligence of service calls through routing tags and grouping, and the client can provide routing support for consumers through multi-dimensional attributes; filters the routing tag information based on the routing tag combination, calling area and calling environment information, determines the routing group list, and through precise routing selection based on labels, can automatically match routes based on the business needs of the consumer and the tag information, thereby achieving precise and efficient service routing selection; and performs service calls for the service consumer based on the routing group list. The existing cloud native platform is unable to establish a flexible routing selection mechanism and provide technical problems for service call performance. Through precise routing selection based on labels, it is possible to ensure efficient and accurate routing selection in complex business scenarios, improve calling efficiency, reduce latency, and effectively enhance the stability and adaptability of the system.

[0068] Figure 3 The present invention provides a flowchart of another service deployment and routing method based on a cloud native platform. This embodiment specifically introduces the specific process of the consumer end performing a service call for the service consumer, such as Figure 3 As shown:

[0069] S310: Receive packet routing information and routing tag information sent by the server.

[0070] S320: Process the routing tag combination of the service consumer, and read the calling area and calling environment information of the service consumer.

[0071] S330: Filter the routing tag information based on the routing tag combination, the calling area, and the calling environment information to determine a routing group list.

[0072] S340: If there is at least one group routing information in the routing group list, each group routing information is selected by polling to perform service call.

[0073] Optionally, after obtaining the routing group list after routing selection, the client identifies whether there is group routing information in the routing group list. If there is a group routing information in the routing group list, the client calls and deploys the group application for the service consumer based on the group routing information; if there are multiple group routing information in the routing group list, these group routing information are all used as call objects, and the deployment group application is called one by one in a polling access manner.

[0074] Optionally, when there are multiple group routing information in the routing group list, it means that the deployment group applications corresponding to the multiple group routing information can provide services to the service consumer. In each call, one deployment group application is selected to provide services, and in the next call, another deployment group application is selected to provide services. Multiple service calls are evenly distributed to each deployment group application to achieve load balancing of the deployment group applications.

[0075] Specifically, the routing tag information is filtered based on the routing tag combination, the calling area, and the calling environment information to determine the routing group list.

[0076] Optionally, in another optional embodiment of the present invention, the performing a service call for the service consumer based on the routing group list further includes:

[0077] If there is no group routing information in the routing group list, updating the routing tag combination based on the first tag priority and / or the second tag priority of each routing tag to determine an updated routing tag combination;

[0078] Return to the step of selecting the selectable packet routes according to the routing tag combination and determining the routing group list until at least one packet routing information exists in the routing group list.

[0079] Optionally, in the present invention, there may not be a group routing information in the routing group list of the service consumer, which means that none of the deployment group applications of the cloud original platform corresponding to the consumer end meets the needs of the service consumer. In order to ensure service support for the service consumer, the client needs to downgrade the second tag priority and / or the first tag priority of the routing tag based on the service consumer, and select an available deployment group application for the service consumer.

[0080] Optionally, when performing downgrade selection for a service consumer, if a second tag priority for a routing tag is set in the routing tag combination of the service consumer, the routing tag with the lowest second tag priority in the routing tag combination is selected as the routing tag to be removed based on the second tag priority of the routing tag, and the routing tag is removed from the routing tag combination to obtain an updated routing tag combination. For example, the routing tag combination provided by the service consumer includes five routing tags. Based on the second tag priorities of the five routing tags, one routing tag is selected for removal to obtain an updated routing tag combination, and the updated routing tag combination consists of four routing tags.

[0081] Optionally, in another scenario, when performing downgrade selection for a service consumer, if the second tag priority of the routing tag is not set in the routing tag combination of the service consumer, the first tag priority of the routing tag is obtained, and based on the first tag priority of the routing tag, the routing tag with the lowest first tag priority in the routing tag combination is selected as the routing tag to be removed. This routing tag is removed from the routing tag combination to obtain an updated routing tag combination. For example, the routing tag combination provided by the service consumer includes four routing tags, none of which have a second tag priority set. Based on the first tag priority of the four routing tags, one routing tag is selected for removal to obtain an updated routing tag combination, and the updated routing tag combination consists of three routing tags.

[0082] Optionally, in another scenario, when performing downgrade selection for a service consumer, if some routing tags in the service consumer's routing tag combination have the second tag priority set, while some routing tags have the first tag priority set, then the routing tags with the second tag priority are preferentially retained, and the routing tags to be removed are selected from the routing tags that do not have the second tag priority set. The method for selecting the routing tags to be removed refers to the selection process for the first tag priority, and the routing tags are removed from the routing tag combination to obtain an updated routing tag combination. For example, the routing tag combination provided by the service consumer has 6 routing tags, 2 of which have the second tag priority set, and 4 of which do not have the second tag priority set. Based on the first tag priority of the 4 routing tags, a routing tag is selected for removal to obtain an updated routing tag combination, and the updated routing tag combination consists of 5 routing tags.

[0083] Optionally, after obtaining the updated routing tag combination, return to execute the steps of routing the selectable group route according to the routing tag combination, determine the routing group list, re-route the selectable group route based on the updated routing tag combination, obtain the updated routing group list, and continue to identify whether there is a group routing information in the updated routing group list. If there is a group routing information in the updated routing group list, perform a service call based on the group routing information. If there is no group routing information in the updated routing group list, repeat the downgrading and updating of the routing tag combination based on the first tag priority and / or the second tag priority of each routing tag, determine the updated routing tag combination and return to execute the steps of routing the selectable group route according to the routing tag combination, determine the routing group list, until there is at least one group routing information in the routing group list.

[0084] Specifically, after obtaining the routing group list after routing selection, the client identifies whether there is group routing information in the routing group list. If there is no group routing information in the routing group list, the routing tag combination is updated based on the first tag priority and / or second tag priority of each routing tag, and the updated routing selection tag combination is determined; the client returns to execute the steps of routing the selectable group routes according to the routing selection tag combination and determining the routing group list until there is at least one group routing information in the routing group list.

[0085] The technical solution of the embodiment of the present invention receives the group routing information and routing tag information sent by the service end; processes the routing tag combination of the service consumer, and reads the calling area and calling environment information of the service consumer; improves the flexibility, standardization and intelligence of service calls through routing tags and grouping, and the client can provide routing support for consumers through multi-dimensional attributes; filters the routing tag information based on the routing tag combination, calling area and calling environment information, determines the routing group list, and through precise routing selection based on labels, can automatically match routes based on the business needs of the consumer and the tag information, thereby achieving precise and efficient service routing selection; and performs service calls for the service consumer based on the routing group list. The existing cloud native platform is unable to establish a flexible routing selection mechanism and provide technical problems for service call performance. Through precise routing selection based on labels, it is possible to ensure efficient and accurate routing selection in complex business scenarios, improve calling efficiency, reduce latency, and effectively enhance the stability and adaptability of the system.

[0086] Figure 4 The embodiment of the present invention provides a flowchart of another service deployment and routing method based on a cloud native platform. This embodiment specifically introduces the specific process of dynamically adjusting the service call strategy based on the deployment group application's response request to the service consumer during the service call for the service consumer. Figure 3 As shown:

[0087] S410: Obtain service call information of at least one of the deployed group applications on the service consumer in real time.

[0088] Optionally, when the consumer calls each deployment group application for the service consumer, it monitors the performance and status of each deployment group application in real time, records the time of each deployment group application call, the deployment group application response status and response time, and obtains the load information of each deployment group application. The response status can be either call success or call failure.

[0089] Among them, the service call information includes service call status and service call response performance. The service call status can be the percentage of successful deployment group application calls to the total number of calls, that is, the success rate of deployment group application calls; the service call response performance can be the response time and load information of the deployment group application.

[0090] Specifically, the service call information of each deployment group application to the service consumer is obtained in real time.

[0091] S420: Build a service performance view based on the service call status and the service call response performance.

[0092] The service performance view can be used by the client to monitor and analyze the visual performance indicator data of each deployed group application. The service performance view can intuitively reflect the service call response performance and service call status of each deployed group application.

[0093] Optionally, in the present invention, indicators of multiple dimensions of the service performance view are set. The main dimensions can be the success rate, response time, and load dimensions. Other dimensions can be selected from dimensions such as delay time and failure rate. Specific data of each deployment group application in each dimension is collected, and the visualization view type and user interaction function of the service performance view are set. The specific data of each deployment group application in each dimension is then converted into a visualization view to obtain a service performance view. Exemplarily, the user interaction function can choose to view the indicators of each dimension of a deployment group application in different time periods; it can also select the comparison of indicators of each dimension of two deployment group applications in the same time period; and it also supports the selection of the type and number of indicators to be displayed.

[0094] Specifically, the service call response performance and service call status construct a service performance view.

[0095] S430: For each of the deployed grouped applications, determine a routing service result of the deployed grouped application based on the service performance view.

[0096] The routing service result can be the response of each deployment group application when a service consumer invokes a service. It should be noted that the routing service result can be used to indicate whether the deployment group application is able to provide services. The routing service result can be either healthy or unhealthy. If the routing service result is unhealthy, the deployment group application is considered unable to provide services; if the routing service result is healthy, the deployment group application can continue to provide services.

[0097] Optionally, for each deployment group application, the client calls the deployment group application once, analyzes the calling status of the deployment group application based on the service performance view, and determines the routing service result corresponding to each deployment group application.

[0098] S440: Update the routing group list based on the routing service result to obtain an updated routing group list.

[0099] Optionally, for a deployment group application called by a service consumer, if the routing service result of the deployment group application is unhealthy, the client needs to isolate the deployment group application and remove the group routing information of the deployment group application from the routing group list to update the routing group list; if the routing service result is healthy, the deployment group application will provide services.

[0100] Optionally, after the deployment group application in the routing group list is isolated, a certain isolation waiting time is set. During the isolation waiting time, the deployment group application will not be called by the client. When the isolation time of each deployment group application is greater than the isolation waiting time, the client will dynamically detect each isolated deployment group application. When the routing service result of a deployment group application is detected to be healthy, it is considered that the deployment group application has returned to normal, and the group routing information of the deployment group application can be added back to the routing group list to obtain an updated routing group list. Based on the updated routing group list, a service call is made for the service consumer. When it is detected that the routing service result of a deployment group application is still unhealthy, the isolation waiting time of the deployment group application is refreshed until the routing service result of the isolated deployment group application is detected to be healthy.

[0101] Optionally, after removing the group routing information of one or more isolated deployment group applications from the routing group list, when the client finds that there is no available group routing information in the routing group list, the client needs to downgrade the second tag priority and / or the first tag priority of the routing tag based on the service consumer, and select an available deployment group application for the service consumer; then return to execute the update of the routing tag combination based on the first tag priority and / or the second tag priority of each routing tag, and determine the updated routing selection tag combination; return to execute the steps of routing selection of the optional group routes according to the routing selection tag combination, and determine the routing group list, until there is at least one group routing information in the routing group list.

[0102] Optionally, after downgrading selection for the service consumer, the obtained routing group list is able to provide services for the service consumer, and a callable time is set for the group routing information obtained for the downgrade selection. After the callable time of a group routing information ends, if it is detected that the group routing information of the deployed group application that was isolated before the downgrade selection exists in the routing group list, the group routing information whose callable time ends is removed from the routing group list; if the group routing information of the deployed group application that was isolated before the downgrade selection exists in the routing group list, the callable time of the group routing information is refreshed. The callable time and the isolation waiting time can be set to the same time value, or different time values ​​can be set. The dynamic update of the routing group list is guaranteed by the client to achieve efficient and reliable service calls.

[0103] S450: Obtain historical call records of each deployed group application, perform call planning on the routing group list according to the historical call records and the service performance view through a preset routing intelligent calculation model, and determine the dynamic call strategy.

[0104] The historical call record may be record data of a deployment group application being called before the current time point. The historical call record records service call information of a deployment group application during a historical time period.

[0105] The intelligent routing calculation model can be a calculation model pre-set by the client to generate an optimal routing call plan for the service consumer. It should be noted that the intelligent routing calculation model can set the call order of each deployment group application in the routing group list based on real-time dynamic data from various dimensions in the service performance view to obtain a dynamic call strategy.

[0106] The dynamic call strategy can be the call priority and call order of each deployment group application in the routing group list. It should be noted that when generating the dynamic call strategy, the routing intelligent calculation model refers to the historical call records of each deployment group application under different indicators to improve the accuracy of the dynamic call strategy;

[0107] Specifically, the historical call records of each deployment group application are obtained, and a preset routing intelligent calculation model is used to perform call planning on the routing group list based on the historical call records and service performance view to determine the dynamic call strategy. For example, taking the three dimensions of success rate, response time, and load as an example, there are three deployment group applications in the routing group list, namely A, B, and C, with success rates of 70%, 80%, and 90%, respectively; response times of 2ms, 20ms, and 200ms, respectively, and loads of 10%, 20%, and 50%, respectively; in the current situation, the dynamic call strategy prioritizes the call sequence of B, C, and A; when the load becomes 20%, 80%, and 60%, respectively, the dynamic call strategy prioritizes the call sequence of C, B, and A; when the load becomes 0%, 90%, and 80%, respectively, the dynamic call strategy prioritizes the call sequence of A, C, and B.

[0108] Optionally, in another optional embodiment of the present invention, performing call planning on the routing group list according to the historical call records and the service performance view using a preset routing intelligent calculation model to determine the dynamic call strategy includes:

[0109] Performing a route selection combination on the route grouping list according to the historical call records and the service performance view through a preset route intelligent calculation model to determine an optimal route selection list;

[0110] The dynamic calling strategy is determined by a preset routing intelligent calculation model based on the routing tag combination and the optimal routing list.

[0111] The best routing list can be a routing list composed of routing information with priority. It should be noted that the response performance of each routing information group in the routing group list is identified by the routing intelligent calculation model, and the routing selection combination is performed in the routing group list to obtain the best routing list.

[0112] Optionally, when generating a dynamic call strategy, the preset routing intelligent calculation model takes into account the business needs and environmental changes of the service consumer, and based on the routing tags of each dimension in the routing selection tag combination, selects the group routing information corresponding to the routing tag with a higher priority in the optimal routing selection list to generate a dynamic call strategy.

[0113] Specifically, a preset routing intelligent calculation model is used to combine routing group lists according to historical call records and service performance views to determine the best routing list, and a dynamic calling strategy is determined based on the routing tag combination and the best routing list.

[0114] S460: Perform service invocation for the service consumer based on the dynamic invocation strategy.

[0115] Specifically, the consumer side performs service calls for the service consumer based on a dynamic call strategy.

[0116] Optionally, in another optional embodiment of the present invention, when it is detected that the service call information of one of the deployed group applications has a service anomaly, the group routing information of the deployed group application is determined as an abnormal group routing, and an alternative group routing is determined based on the routing group list;

[0117] updating the dynamic invocation policy based on the abnormal packet routing and the alternative packet routing, and determining an updated dynamic invocation policy;

[0118] A service call is performed for the service consumer based on the updated dynamic call strategy.

[0119] Among them, service anomaly can be understood as an anomaly in the service call information of a group routing information. For example, taking the success rate in the service call information as an example, if the success rate of deploying the group application changes from 99% to 10%, the deployment group application is considered to be a service anomaly.

[0120] The abnormal group routing may be service call information of a service abnormality; the abnormal group routing may be used to indicate that the deployment group application will not be called.

[0121] The alternative packet route may be a normal service packet route in the routing group list. It should be noted that when a service abnormality is detected in the service call information, a route check is performed in the routing group list, and a normal service call information is detected as the alternative packet route.

[0122] Optionally, if no alternative group route can be found in the routing group list, return to executing the update of the routing tag combination based on the first tag priority and / or the second tag priority of each routing tag, and determine the updated routing selection tag combination; return to executing the step of routing selection of the selectable group routes according to the routing selection tag combination, and determining the routing group list, until there is a normal service call information in the routing group list as the alternative group route.

[0123] Optionally, when determining an alternative packet route for the abnormal packet route, the abnormal packet route is replaced by the alternative packet route in the dynamic invocation policy to update the dynamic invocation policy to obtain a new dynamic invocation policy.

[0124] Specifically, when the client's early warning mechanism detects a service anomaly in the service call information of a deployed group application, it identifies the deployed group application's group routing information as an abnormal group routing and determines an alternative group routing based on the routing group list. The dynamic call policy is updated based on the abnormal group routing and the alternative group routing, and an updated dynamic call policy is determined. The service call is then made for the service consumer based on the updated dynamic call policy. Through the client's intelligent computing and planning capabilities, the optimal routing call solution is automatically generated, improving the efficiency and reliability of service calls. This method can adaptively perform dynamic planning based on varying business needs and environmental changes.

[0125] Optionally, after the client completes the service call for the service consumer, the client calls the service consumer's call result and analyzes it to update the preset routing intelligent calculation model to optimize future routing selection and call planning.

[0126] The technical solution of the embodiment of the present invention receives the group routing information and routing tag information sent by the service end; processes the routing selection tag combination of the service consumer, and reads the calling area and calling environment information of the service consumer; improves the flexibility, standardization and intelligence of service calls through routing tags and grouping, and the client can provide routing support for consumers through multi-dimensional attributes; filters the routing tag information based on the routing selection tag combination, calling area and calling environment information, determines the routing group list, and through precise routing selection based on tags, can automatically match routes based on the business needs of the consumer and tag information, thereby achieving precise and efficient service routing selection; and performs service calls for the service consumer based on the routing group list. The existing cloud native platform is unable to establish a flexible routing selection mechanism and provide technical problems for service call performance. Through precise routing selection based on tags, it is possible to ensure efficient and accurate routing selection in complex business scenarios, improve calling efficiency, reduce latency, and effectively enhance the stability and adaptability of the system.

[0127] Figure 5 The present invention provides a flowchart of another method for service deployment and routing based on a cloud native platform. This embodiment can be applied to a server, which can mark routes for service applications deployed on the cloud native platform and push each service application to the client. The method can be executed by a service deployment and routing device based on a cloud native platform. The service deployment and routing device based on a cloud native platform can be implemented in the form of hardware and / or software. The service deployment and routing device based on a cloud native platform can be configured in the server. Figure 5 As shown, the method includes:

[0128] S510: Receive at least one deployment group application of a service application deployed by a service provider on a cloud native platform and group routing information of the deployment group application.

[0129] Optionally, the service provider splits the service application into multiple deployment group applications for deployment on the cloud native platform, and sets group routing information for each deployment group application. The cloud native platform generates a creation event for each deployment group application.

[0130] Optionally, the service provider can also update or delete the deployed group application and the group routing information of the deployed group application on the cloud native platform, and the cloud native platform will generate corresponding update events and deletion events.

[0131] Specifically, the server retrieves the creation event of each deployment group application in real time through the API of the cloud native platform to receive at least one deployment group application of the service application deployed by the service provider on the cloud native platform and the group routing information of the deployment group application.

[0132] S520: For each of the deployment group applications, set routing tag information for the deployment group application based on a preset tagging method.

[0133] The preset marking method may be a pre-set labeling rule for setting labels; the preset labeling method can be used to add metadata labels of different dimensions to obtain routing labels of various dimensions.

[0134] Optionally, after receiving the deployment group application and group routing information, the server performs multi-dimensional tagging on the acquired group routing information based on a preset tagging method for each deployment group application to obtain routing tag information corresponding to each group routing information.

[0135] S530: Push the group routing information and the routing tag information of each deployed group application to the client.

[0136] Specifically, the server pushes the group routing information and routing mark information of each deployed group application to the client using an efficient push channel.

[0137] Optionally, the server retrieves the update events and deletion events of each deployed group application in real time through the API of the cloud native platform, updates the group routing information of the deployed group application corresponding to the update event based on the update event, and pushes it to the client; deletes the group routing information of the deployed group application corresponding to the deletion event, and pushes it to the client.

[0138] Optionally, the server has routing liveness detection and monitoring capabilities, which can regularly detect the health status of each deployed group application, proactively send liveness detection requests, and monitor the service response time and status. If the liveness detection fails, the group routing information of the deployed group application is automatically marked as unavailable, and the client is notified in real time via a push channel, allowing for rapid routing adjustments to ensure the reliability and stability of service calls.

[0139] The technical solution of the embodiment of the present invention receives the group routing information and routing tag information sent by the service end; processes the routing selection tag combination of the service consumer, and reads the calling area and calling environment information of the service consumer; improves the flexibility, standardization and intelligence of service calls through routing tags and grouping, and the client can provide routing support for consumers through multi-dimensional attributes; filters the routing tag information based on the routing selection tag combination, calling area and calling environment information, determines the routing group list, and through precise routing selection based on tags, can automatically match routes based on the business needs of the consumer and tag information, thereby achieving precise and efficient service routing selection; and performs service calls for the service consumer based on the routing group list. The existing cloud native platform is unable to establish a flexible routing selection mechanism and provide technical problems for service call performance. Through precise routing selection based on tags, it is possible to ensure efficient and accurate routing selection in complex business scenarios, improve calling efficiency, reduce latency, and effectively enhance the stability and adaptability of the system.

[0140] Figure 6 A schematic diagram of a service deployment and routing device based on a cloud native platform provided by an embodiment of the present invention. Figure 6 As shown, the device includes: a communication module 610, a processing module 620, a grouping module 630 and a calling module 640; wherein,

[0141] Communication module 610, used to receive packet routing information and routing tag information sent by the server;

[0142] Processing module 620, configured to process the routing tag combination of the service consumer and read the calling region and calling environment information of the service consumer; wherein the routing tag combination includes packet routing information and the routing tag combination;

[0143] A grouping module 630 is configured to filter the routing tag information based on the routing tag combination, the calling region, and the calling environment information to determine a routing grouping list;

[0144] The calling module 640 is configured to call a service for the service consumer based on the routing group list.

[0145] The technical solution of the embodiment of the present invention receives the group routing information and routing tag information sent by the service end; processes the routing selection tag combination of the service consumer, and reads the calling area and calling environment information of the service consumer; improves the flexibility, standardization and intelligence of service calls through routing tags and grouping, and the client can provide routing support for consumers through multi-dimensional attributes; filters the routing tag information based on the routing selection tag combination, calling area and calling environment information, determines the routing group list, and through precise routing selection based on tags, can automatically match routes based on the business needs of the consumer and tag information, thereby achieving precise and efficient service routing selection; and performs service calls for the service consumer based on the routing group list. The existing cloud native platform is unable to establish a flexible routing selection mechanism and provide technical problems for service call performance. Through precise routing selection based on tags, it is possible to ensure efficient and accurate routing selection in complex business scenarios, improve calling efficiency, reduce latency, and effectively enhance the stability and adaptability of the system.

[0146] Optionally, the grouping module 630 is specifically configured to: filter the routing tag information according to the calling area and the calling environment information to determine selectable grouping routes;

[0147] The selectable packet routes are selected according to the routing tag combination to determine the routing group list.

[0148] Optionally, the calling module 640 is specifically configured to: if there is at least one group routing information in the routing group list, then poll and select each group routing information to perform service calling.

[0149] Optionally, the calling module 640 is specifically configured to: the routing tag information includes at least one routing tag and a first tag priority corresponding to each routing tag; the routing selection tag combination includes at least one routing tag and a second tag priority of each routing tag;

[0150] If there is no group routing information in the routing group list, updating the routing tag combination based on the first tag priority and / or the second tag priority of each routing tag to determine an updated routing tag combination;

[0151] Return to the step of selecting the selectable packet routes according to the routing tag combination and determining the routing group list until at least one packet routing information exists in the routing group list.

[0152] The device also includes a real-time monitoring module, a visualization module, a call processing module, a group update module, a strategy planning module and a call update module; wherein,

[0153] A real-time monitoring module, configured to obtain in real time service call information of at least one of the deployed group applications on the service consumer; wherein the service call information includes service call status and service call response performance;

[0154] A visualization module, configured to construct a service performance view based on the service call response performance and the service call status;

[0155] A calling processing module is used to determine, for each of the deployment group applications, a routing service result of the deployment group application based on the service performance view;

[0156] A grouping update module, configured to update the routing grouping list based on the routing service result to obtain an updated routing grouping list;

[0157] a strategy planning module, configured to obtain historical call records of each deployed group application, perform call planning on the routing group list based on the historical call records and the service performance view using a preset routing intelligent calculation model, and determine the dynamic call strategy;

[0158] A call update module is used to perform service calls for the service consumer based on the dynamic call strategy.

[0159] Optionally, the strategy planning module is specifically used to:

[0160] Performing a route selection combination on the route grouping list according to the historical call records and the service performance view through a preset route intelligent calculation model to determine an optimal route selection list;

[0161] The dynamic calling strategy is determined by a preset routing intelligent calculation model based on the routing tag combination and the optimal routing list.

[0162] Optionally, the strategy planning module is further configured to:

[0163] When detecting that the service call information of one of the deployed group applications has a service anomaly, determining the group routing information of the deployed group application as an abnormal group routing, and determining an alternative group routing based on the routing group list;

[0164] updating the dynamic invocation policy based on the abnormal packet routing and the alternative packet routing, and determining an updated dynamic invocation policy;

[0165] A service call is performed for the service consumer based on the updated dynamic call strategy.

[0166] The service deployment and routing device based on the cloud native platform provided in the embodiment of the present invention can execute the service deployment and routing method based on the cloud native platform provided in any embodiment of the present invention, and has the functional modules and beneficial effects corresponding to the execution method.

[0167] Figure 7 This is a schematic diagram of another service deployment and routing device based on a cloud native platform provided by an embodiment of the present invention. Figure 7 As shown, the device includes: a platform connection module 710, a processing module 720 and a push module 730; wherein,

[0168] The platform connection module 710 is configured to receive at least one deployment group application of a service application deployed by a service provider on a cloud native platform and group routing information of the deployment group application;

[0169] The processing module 720 is configured to set routing tag information for each of the deployment group applications based on a preset tagging method;

[0170] The push module 730 is configured to push the group routing information and the routing tag information of each deployed group application to the client.

[0171] The technical solution of the embodiment of the present invention receives the group routing information and routing tag information sent by the service end; processes the routing selection tag combination of the service consumer, and reads the calling area and calling environment information of the service consumer; improves the flexibility, standardization and intelligence of service calls through routing tags and grouping, and the client can provide routing support for consumers through multi-dimensional attributes; filters the routing tag information based on the routing selection tag combination, calling area and calling environment information, determines the routing group list, and through precise routing selection based on tags, can automatically match routes based on the business needs of the consumer and tag information, thereby achieving precise and efficient service routing selection; and performs service calls for the service consumer based on the routing group list. The existing cloud native platform is unable to establish a flexible routing selection mechanism and provide technical problems for service call performance. Through precise routing selection based on tags, it is possible to ensure efficient and accurate routing selection in complex business scenarios, improve calling efficiency, reduce latency, and effectively enhance the stability and adaptability of the system.

[0172] The service deployment and routing device based on the cloud native platform provided in the embodiment of the present invention can execute the service deployment and routing method based on the cloud native platform provided in any embodiment of the present invention, and has the functional modules and beneficial effects corresponding to the execution method.

[0173] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in the present invention can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of the present invention can be achieved. This is not limited herein.

[0174] The above specific embodiments do not limit the scope of protection of the present invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention are intended to be included within the scope of protection of the present invention.

Claims

1. A service deployment and routing method based on a cloud native platform, characterized in that: Applied to the client; includes: Receive packet routing information and routing tag information sent by the server; Processing the routing tag combination of the service consumer and reading the calling region and calling environment information of the service consumer; Filtering the routing tag information based on the routing tag combination, the calling area, and the calling environment information to determine a routing group list; A service call is made for the service consumer based on the routing group list.

2. The method according to claim 1, characterized in that The filtering of the routing tag information based on the routing tag combination, the calling area, and the calling environment information to determine the routing group list includes: filtering the routing tag information according to the calling area and the calling environment information to determine an optional grouping route; The selectable packet routes are selected according to the routing tag combination to determine the routing group list.

3. The method according to claim 2, characterized in that The performing a service call for the service consumer based on the routing group list includes: If there is at least one group routing information in the routing group list, each group routing information is selected in a polling manner to perform a service call.

4. The method according to claim 3, characterized in that The routing tag information includes at least one routing tag and a first tag priority corresponding to each routing tag; the routing selection tag combination includes at least one routing tag and a second tag priority corresponding to each routing tag; Also includes: If there is no group routing information in the routing group list, updating the routing tag combination based on the first tag priority and / or the second tag priority of each routing tag to determine an updated routing tag combination; Return to the step of selecting the selectable packet routes according to the routing tag combination and determining the routing group list until at least one packet routing information exists in the routing group list.

5. The method according to claim 1, wherein After calling a service for the service consumer based on the routing group list, the method further includes: Acquire service call information of at least one deployment group application to the service consumer in real time; wherein the service call information includes service call status and service call response performance; Building a service performance view based on the service call status and service call response performance; For each of the deployment group applications, determining a routing service result of the deployment group application based on the service performance view; updating the routing group list based on the routing service result to obtain an updated routing group list; Obtain historical call records of each deployed group application, perform call planning on the routing group list based on the historical call records and the service performance view using a preset routing intelligent calculation model, and determine a dynamic call strategy; Perform service calls for the service consumer based on the dynamic call strategy.

6. The method according to claim 5, characterized in that The method of performing call planning on the routing group list according to the historical call records and the service performance view by using a preset routing intelligent calculation model to determine the dynamic call strategy includes: Performing a route selection combination on the route grouping list according to the historical call records and the service performance view through a preset route intelligent calculation model to determine an optimal route selection list; The dynamic calling strategy is determined by a preset routing intelligent calculation model based on the routing tag combination and the optimal routing list.

7. The method according to claim 5, characterized in that Also includes: When detecting that the service call information of one of the deployed group applications has a service anomaly, determining the group routing information of the deployed group application as an abnormal group routing, and determining an alternative group routing based on the routing group list; updating the dynamic invocation policy based on the abnormal packet routing and the alternative packet routing, and determining an updated dynamic invocation policy; A service call is performed for the service consumer based on the updated dynamic call strategy.

8. A service deployment and routing method based on a cloud native platform, characterized in that: Applied to the server; including: receiving at least one deployment group application of a service application deployed by a service provider on a cloud native platform and group routing information of the deployment group application; For each of the deployment group applications, setting routing tag information for the deployment group application based on a preset tagging method; The group routing information and the routing tag information of each of the deployed group applications are pushed to the client.

9. A service deployment and routing device based on a cloud native platform, characterized in that: Deployed on the client; includes: The communication module is used to receive the packet routing information and routing mark information sent by the server; A processing module, configured to process a routing tag combination of a service consumer and read the calling region and calling environment information of the service consumer; wherein the routing tag combination includes packet routing information and a routing tag combination; A grouping module, configured to filter the routing tag information based on the routing tag combination, the calling area, and the calling environment information, and determine a routing grouping list; A calling module is used to call a service for the service consumer based on the routing group list.

10. A service deployment and routing device based on a cloud native platform, characterized in that: Deployed on the server; including: a platform connection module, configured to receive at least one deployment group application of a service application deployed by a service provider on a cloud native platform and group routing information of the deployment group application; a processing module, configured to set routing tag information for each of the deployment group applications based on a preset tagging method; A push module is used to push the group routing information and the routing tag information of each deployed group application to the client.

Images