CN117170718B - Gray scale release method and device based on micro-service architecture and electronic equipment - Google Patents
Gray scale release method and device based on micro-service architecture and electronic equipment Download PDFInfo
- Publication number
- CN117170718B CN117170718B CN202311443111.5A CN202311443111A CN117170718B CN 117170718 B CN117170718 B CN 117170718B CN 202311443111 A CN202311443111 A CN 202311443111A CN 117170718 B CN117170718 B CN 117170718B
- Authority
- CN
- China
- Prior art keywords
- gray
- service
- gray scale
- target
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本发明涉及灰度发布技术领域，揭露了一种基于微服务架构的灰度发布方法，包括：根据灰度前端的配置信息指定灰度发布的灰度对象名单，配置版本路由规则，根据版本路由规则动态同步更新所述本地路由规则，得到网关路由规则，根据所述操作请求的前端资源信息和灰度对象名单筛选操作请求，得到灰度请求，将灰度请求路由至所述目标灰度服务，并运行目标灰度服务，得到灰度请求反馈，根据所述灰度请求反馈调整目标灰度服务，更新灰度对象名单。本发明还提出一种基于微服务架构的灰度发布装置及电子设备。本发明可以解决当前通过Nginx负载均衡算法实现灰度发布存在着运维成本高、无法灵活配置灰度用户组的问题。
The present invention relates to the technical field of grayscale publishing, and discloses a grayscale publishing method based on a microservice architecture, which includes: specifying a grayscale object list for grayscale publishing according to the configuration information of the grayscale front end, configuring version routing rules, and routing according to the version The rules dynamically update the local routing rules to obtain the gateway routing rules, filter the operation requests according to the front-end resource information and the grayscale object list of the operation request, obtain the grayscale request, and route the grayscale request to the target grayscale service. , and run the target grayscale service, obtain grayscale request feedback, adjust the target grayscale service according to the grayscale request feedback, and update the grayscale object list. The present invention also proposes a grayscale publishing device and electronic equipment based on microservice architecture. The present invention can solve the current problems of high operation and maintenance costs and inability to flexibly configure grayscale user groups when implementing grayscale publishing through the Nginx load balancing algorithm.
Description
Technical Field
The present invention relates to the field of gray level publishing technologies, and in particular, to a gray level publishing method and device based on a micro-service architecture, and an electronic device.
Background
Gray level distribution refers to a distribution manner capable of smoothly transiting between black and white, and is used for gradually introducing new version software functions or improvements into partial users or servers in a production environment so as to ensure the stability and reliability of a system. The micro service architecture is a new software architecture model, splitting a large complex application into a set of mutually independent small services, each of which focuses on a specific business function and communicates through a well-defined interface.
Currently, the gray level release is realized by distributing target services according to an algorithm rule through an Nginx load balancing algorithm. However, the operation and maintenance cost for realizing gray level release by using the Nginx load balancing algorithm is high, and a user-defined gray level user group cannot be realized, and only the gray level release can be carried out according to a certain rule such as a source or a flow ratio, so that the problem that the operation and maintenance cost is high and the gray level user group cannot be flexibly configured exists in the current gray level release realized by using the Nginx load balancing algorithm.
Disclosure of Invention
The invention provides a gray level release method device based on a micro-service architecture and electronic equipment, and mainly aims to solve the problems that the operation and maintenance cost is high and gray level user groups cannot be flexibly configured when gray level release is realized through an Nginx load balancing algorithm at present.
In order to achieve the above object, the present invention provides a gray level publishing method based on a micro-service architecture, comprising:
designating an initial gray scale service and a gray scale front end of gray scale release according to a preset gray scale release plan, and configuring a gray scale release version by utilizing the initial gray scale service and the gray scale front end;
acquiring configuration information of a gray level front end, and designating a service object of gray level release according to the configuration information of the gray level front end to obtain a gray level object list;
registering the initial gray scale service into Nacos to obtain a target gray scale service, acquiring a configuration file of the Nacos, and designating a gray scale version number of the target gray scale service by using the configuration file of the Nacos;
the obtaining the configuration file of the Nacos, and designating the gray scale version number of the target gray scale service by using the configuration file of the Nacos comprises the following steps:
receiving a configuration file acquisition instruction, and constructing a secure connection with a pre-constructed Nacos configuration service;
extracting identification information of a target gray scale service from the configuration file acquisition instruction, and acquiring a configuration file of Nacos according to the identification information;
analyzing the configuration file of the Nacos to obtain configuration information related to the target gray scale service;
identifying a gray scale version number of the target gray scale service from the configuration information;
Acquiring configuration information and local routing rules of a target gray scale service, configuring version routing rules by using the configuration information and gray scale version number of the target gray scale service, and dynamically and synchronously updating the local routing rules according to the version routing rules to obtain gateway routing rules;
based on Spring Cloud Gateway gateway receiving operation request, obtaining front end resource information of the operation request, screening the operation request according to the front end resource information of the operation request and the gray object list, and obtaining gray request;
the method comprises the steps of obtaining version information of a gray request, routing the gray request to a target gray service according to the version information of the gray request and a gateway routing rule in a gray release version, and operating the target gray service to obtain gray request feedback, wherein the target gray service is identical to a gray version number and a URL path of the gray request;
and feeding back and adjusting the target gray scale service according to the gray scale request, updating a gray scale object list, and finishing gray scale release based on a micro-service architecture.
Optionally, the configuring the gray scale release version by using the initial gray scale service and the gray scale front end includes:
creating an initial gray scale environment, and introducing the initial gray scale service and the gray scale front end into the initial gray scale environment to obtain a target gray scale environment;
And putting the target gray environment into a pre-constructed service platform to obtain a gray release version.
Optionally, the service object of the gray level release is specified according to the configuration information of the gray level front end, and a gray level object list is obtained, including:
extracting the IP address of the gray level front end from the configuration information of the gray level front end to obtain a target gray level IP address;
acquiring a service object with the target gray IP address, and designating the service object as a gray object;
and summarizing the gray objects to obtain a gray object list.
Optionally, registering the initial gray scale service in the Nacos to obtain the target gray scale service includes:
acquiring service information of an initial gray scale service, creating an initial Servicelnstance instance, and configuring the service information of the initial gray scale service in the initial Servicelnstance instance to obtain a target Servicelnstance instance;
adding a Nacos Client SDK, and initializing Nacos configuration by using the Nacos Client SDK to obtain initial Nacos configuration;
the initial Nacos are utilized to configure a port of the designated Nacos, and a gray service registration port is obtained;
calling a registerlnstance method preset in a Nacos Client SDK according to a target Servicelstance instance, and registering an initial gray service in the Nacos by using the registerlnstance method and a gray service registration port to obtain a target gray service.
Optionally, the configuring the version routing rule by using the configuration information and the gray version number of the target gray service dynamically and synchronously updates the local routing rule according to the version routing rule to obtain a gateway routing rule, which includes:
extracting a gray scale version number and a URL path of the target gray scale service from the configuration information of the target gray scale service;
creating a route configuration space according to the gray version number of the target gray service and the URL path, and setting the gray version number as an interface of the route configuration space;
in the routing configuration space, matching the target gray scale service with the same gray scale version number and URL path with the interface of the routing configuration space to obtain a version routing rule for routing the target gray scale service by using the gray scale version number and the URL path;
and synchronously updating the version routing rule into the local routing rule by using Nacos to obtain a gateway routing rule.
Optionally the Spring Cloud Gateway-based gateway receiving an operation request includes:
acquiring a Maven configuration file, and adding a Spring Cloud Gateway gateway and corresponding dependency items of a pre-constructed Netty framework into the Maven configuration file to obtain Netty dependency;
And creating HTTP by taking the Netty framework as a bottom layer, monitoring and receiving an operation request by utilizing the HTTP based on Netty dependence.
Optionally, the step of screening the operation request according to the front-end resource information of the operation request and the gray object list to obtain a gray request includes:
extracting the IP address of the operation request from the front-end resource information of the operation request;
acquiring configuration information of a gray object list, and extracting an IP address of the gray object list from the configuration information of an initial gray user list;
and extracting the operation request which is the same as the IP address of the gray object list from the operation request according to the IP address of the gray object list and the IP address of the operation request to obtain the gray request.
Optionally, the routing the gray request to the target gray service according to the version information of the gray request and the gateway routing rule, and operating the target gray service to obtain the gray request feedback, including:
creating Gateway configuration classes, and configuring Gateway routing rules into the Spring Cloud Gateway Gateway by using the Gateway configuration classes to obtain target routing rules;
extracting a version number and a URL path of the gray request from the version information of the gray request, and taking the version number of the gray request as a request interface of the Spring Cloud Gateway gateway;
Matching target gray scale service with the same gray scale version number and the same URL path with gray scale request according to a request interface and a target routing rule of the Spring Cloud Gateway gateway;
according to the target routing rule, utilizing a Spring Cloud Gateway gateway to route the gray request to the target gray service;
and operating the target gray service according to the gray request to obtain gray request feedback.
Optionally, the adjusting the target gray scale service according to the gray scale request feedback, updating a gray scale object list, and completing gray scale release based on a micro service architecture includes:
judging whether the target gray service with the same gray version number and the same URL path as the gray request is available service or not according to gray service feedback by utilizing Nacos;
if the target gray scale service is not available service, adjusting the target gray scale service by using Nacos, returning to the step of using Nacos, and judging whether the target gray scale service with the same gray scale version number and the same URL path as the gray scale request is available service according to gray scale service feedback;
if the target gray scale service is available service, acquiring a configuration file of a gray scale object list, and expanding a service object of the target gray scale service by using the configuration file of the gray scale object list to obtain a service user list;
And expanding the range of gray release versions according to the service user list, and realizing gray release based on the micro-service architecture.
In order to solve the above problems, the present invention further provides a gray scale publishing device based on a micro service architecture, the device comprising:
the gray release version configuration module is used for designating an initial gray service and a gray front end of gray release according to a preset gray release plan and configuring a gray release version by utilizing the initial gray service and the gray front end; acquiring configuration information of a gray level front end, and designating a service object of gray level release according to the configuration information of the gray level front end to obtain a gray level object list; registering the initial gray scale service into Nacos to obtain a target gray scale service, acquiring a configuration file of the Nacos, and designating a gray scale version number of the target gray scale service by using the configuration file of the Nacos; the obtaining the configuration file of the Nacos, and designating the gray scale version number of the target gray scale service by using the configuration file of the Nacos comprises the following steps: receiving a configuration file acquisition instruction, and constructing a secure connection with a pre-constructed Nacos configuration service; extracting identification information of a target gray scale service from the configuration file acquisition instruction, and acquiring a configuration file of Nacos according to the identification information; analyzing the configuration file of the Nacos to obtain configuration information related to the target gray scale service; identifying a gray scale version number of the target gray scale service from the configuration information;
The gateway routing module is used for acquiring configuration information and local routing rules of the target gray scale service, configuring version routing rules by utilizing the configuration information and gray scale version number of the target gray scale service, and dynamically and synchronously updating the local routing rules according to the version routing rules to obtain gateway routing rules; based on Spring Cloud Gateway gateway receiving operation request, obtaining front end resource information of the operation request, screening the operation request according to the front end resource information of the operation request and the gray object list, and obtaining gray request; the method comprises the steps of obtaining version information of a gray request, routing the gray request to a target gray service according to the version information of the gray request and a gateway routing rule in a gray release version, and operating the target gray service to obtain gray request feedback, wherein the target gray service is identical to a gray version number and a URL path of the gray request;
and the gray release version release module is used for feeding back and adjusting the target gray service according to the gray request, updating the gray object list and completing gray release based on the micro service architecture.
In order to solve the above-mentioned problems, the present invention also provides an electronic apparatus including:
At least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to implement the micro-service architecture based gray scale distribution method described above.
Compared with the background art, the method comprises the following steps: according to the embodiment of the invention, an initial gray service, a gray front end and a gray object influenced by the gray release version are designated by configuring the gray release version, so that a gray object list is obtained by summarizing the gray object, a gray version number of a target gray service is designated by Nocas, a version routing rule is configured according to the gray version number of the gray service, a local routing rule is updated by Nacos, so as to obtain a gateway routing rule, an operation request of a client is received, a gray request is screened according to the gray object list, the gray request is routed by using a Spring Cloud Gateway gateway, the target gray service is operated, gray request feedback is obtained, the availability of the target gray service is judged according to the gray request feedback, the gray object list is updated, and gray release is realized. Therefore, the gray level release method, the gray level release device and the electronic equipment based on the micro-service architecture can solve the problems that the operation and maintenance cost is high and the gray level user group cannot be flexibly configured when gray level release is realized through the Nginx load balancing algorithm currently.
Drawings
Fig. 1 is a flowchart of a gray level publishing method based on a micro-service architecture according to an embodiment of the present invention;
FIG. 2 is a functional block diagram of a gray scale distribution device based on a micro-service architecture according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of an electronic device for implementing the gray level publishing method based on the micro-service architecture according to an embodiment of the present invention.
The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
The embodiment of the application provides a gray level publishing method based on a micro-service architecture. The execution subject of the gray level publishing method based on the micro-service architecture includes, but is not limited to, at least one of a server, a terminal and the like, which can be configured to execute the method provided by the embodiment of the application. In other words, the gray scale distribution method based on the micro service architecture may be performed by software or hardware installed in a terminal device or a server device. The service end includes but is not limited to: a single server, a server cluster, a cloud server or a cloud server cluster, and the like.
Example 1: referring to fig. 1, a flow chart of a gray level publishing method based on a micro-service architecture according to an embodiment of the invention is shown. In this embodiment, the gray level publishing method based on the micro service architecture includes:
s1, designating an initial gray scale service and a gray scale front end of gray scale release according to a preset gray scale release plan, and configuring a gray scale release version by utilizing the initial gray scale service and the gray scale front end.
The gray level release plan refers to a gray level release target and a new version service needing gray level release, and is exemplified by a set of service A for providing seven layers of services on line, at this time, some new service characteristics are developed, and a version service B containing the new service characteristics needs to be released.
In the embodiment of the invention, the initial gray service refers to a new version service needing gray release, and the gray front end refers to a front end resource of the new version service.
In the embodiment of the present invention, the configuration of the gray release version by using the initial gray service and the gray front end includes:
creating an initial gray scale environment, and introducing the initial gray scale service and the gray scale front end into the initial gray scale environment to obtain a target gray scale environment;
And putting the target gray environment into a pre-constructed service platform to obtain a gray release version.
The gray level release version is a service platform for gray level release, wherein the service platform is a centralized platform for providing services, is used for connecting the services and the service objects, and provides a series of functions and tools for managing and interacting with the services.
It can be explained that the target gray scale environment is a special environment between a development environment and a production environment for executing gray scale release, and new versions can be tested and verified step by step in order. In a greyscale environment, only a part of the users are guided to the new version, the other users still using the old version. The gray level release is carried out by using the gray level environment, so that the influence range of potential problems of the new version service can be limited, and the performance, stability and user experience of the new version service can be checked step by step.
It should be explained that the target gray scale environment has the same configuration and scale as the production environment and similar service environments.
S2, acquiring configuration information of the gray level front end, and designating a service object of gray level release according to the configuration information of the gray level front end to obtain a gray level object list.
The configuration information of the gray level front end includes an IP address of the gray level front end, where the IP address of the gray level front end refers to an IP address used by the client in network communication, and is used for identifying a user, performing geographic location positioning, and security verification, for example: public IP address of the user terminal equipment and private IP address in the local area network.
In the embodiment of the invention, the gray object list refers to a service object list of gray release meeting the condition.
In the embodiment of the present invention, the service object for gray release is specified according to the configuration information of the gray front end, and a gray object list is obtained, which includes:
extracting the IP address of the gray level front end from the configuration information of the gray level front end to obtain a target gray level IP address;
acquiring a service object with the target gray IP address, and designating the service object as a gray object;
and summarizing the gray objects to obtain a gray object list.
And S3, registering the initial gray service into Nacos to obtain a target gray service, acquiring a configuration file of the Nacos, and designating a gray version number of the target gray service by using the configuration file of the Nacos.
The Nacos refers to an open source distributed configuration management and service discovery platform that provides functionality for dynamic configuration management, service registration and discovery. Illustratively, the Nacos can dynamically acquire the configuration and update the routing rules synchronously.
In detail, the Nacos includes a Nacos registry, and can register own services through the Nacos registry and discover other services. Illustratively, the Nacos registers the initial grayscale service to the Nacos registry by calling the registerlnstance method in the Nacos Client SDK.
In the embodiment of the present invention, registering an initial gray scale service in a Nacos to obtain a target gray scale service includes:
acquiring service information of an initial gray scale service, creating an initial Servicelnstance instance, and configuring the service information of the initial gray scale service in the initial Servicelnstance instance to obtain a target Servicelnstance instance;
adding a Nacos Client SDK, and initializing Nacos configuration by using the Nacos Client SDK to obtain initial Nacos configuration;
the initial Nacos are utilized to configure a port of the designated Nacos, and a gray service registration port is obtained;
calling a registerlnstance method preset in a Nacos Client SDK according to a target Servicelstance instance, and registering an initial gray service in the Nacos by using the registerlnstance method and a gray service registration port to obtain a target gray service.
In the embodiment of the present invention, the specifying the gray scale version number of the target gray scale service by using the configuration file of the Nacos includes:
Extracting a gray level configuration item from the configuration file of the Nacos and designating the value of the gray level configuration item to obtain a target configuration value;
and matching the target gray scale service according to the target configuration value to obtain a gray scale version number.
The configuration information of the initial gray service includes service name, IP address, port and URL path.
The URL path is interpreted to mean that in a complete URL, the location or path of the resource to be accessed on the server, usually starts at the first forward slash behind the domain name and ends with a slash or extension of the resource.
The service instance is an object used for representing a service instance in the micro-service architecture, and the attribute of the service instance contains information of the service instance, and the service Host attribute of the service instance represents an IP address of the service instance, so that a client can access related services through the IP address.
The Nacos Client SDK is a Client development kit for Nacos, and is commonly used for communication and interaction with Nacos servers. Illustratively, the Nacos registers the grayscale service to the Nacos registry by calling the registerlnstance method in the Nacos Client SDK.
The gray scale configuration item refers to a configuration attribute for specifying a gray scale service version number, for example: designating the value of the gradation configuration item as 1, the version number of the gradation service is 1.
Optionally, the acquiring the configuration file of the Nacos, and designating the gray scale version number of the target gray scale service by using the configuration file of the Nacos may further include:
receiving a configuration file acquisition instruction, and constructing a secure connection with a pre-constructed Nacos configuration service;
extracting identification information of a target gray scale service from the configuration file acquisition instruction, and acquiring a configuration file of Nacos according to the identification information;
analyzing the configuration file of the Nacos to obtain configuration information related to the target gray scale service;
and identifying the gray scale version number of the target gray scale service from the configuration information.
S4, acquiring configuration information and local routing rules of the target gray scale service, configuring version routing rules by using the configuration information and gray scale version number of the target gray scale service, and dynamically and synchronously updating the local routing rules according to the version routing rules to obtain gateway routing rules.
The routing rule refers to a rule for determining a transmission path of a network packet, and specifies a routing path of the packet from a source address to a destination address, and the version routing rule matches a destination gray scale service of a gray scale request according to a service version number, for example.
In the embodiment of the present invention, the local routing rule refers to a rule defined in the Nacos, including a default rule, a subnet rule, and a source address rule, which are used for determining a forwarding path of a data packet. Illustratively, when no specific rule matches, the system processes according to the default rule and sends the data packet to the default gateway.
In the embodiment of the present invention, the configuring version routing rule by using the configuration information and the gray version number of the target gray service dynamically and synchronously updates the local routing rule according to the version routing rule to obtain a gateway routing rule, including:
extracting a gray scale version number and a URL path of the target gray scale service from the configuration information of the target gray scale service;
creating a routing configuration space according to the gray version number of the target gray service and the URL path, setting the gray version number as an interface of the routing configuration space, and matching the target gray service with the same gray version number and URL path with the interface of the routing configuration space in the routing configuration space to obtain a version routing rule for routing the target gray service by using the gray version number and the URL path;
and synchronously updating the version routing rule into the local routing rule by using Nacos to obtain a gateway routing rule.
S5, receiving an operation request based on the Spring Cloud Gateway gateway, acquiring front-end resource information of the operation request, and screening the operation request according to the front-end resource information of the operation request and the gray object list to obtain a gray request.
Spring Cloud is a framework for building and managing distributed systems, and is a common problem for developing and managing distributed applications. Illustratively, the external requests are routed and filtered using a Spring Cloud Gateway gateway to protect the security and stability of the internal micro-services. Wherein the Spring Cloud Gateway gateway refers to a lightweight, non-blocking, responsive API gateway.
In the embodiment of the invention, the operation request refers to a request that a client applies for obtaining a corresponding target gray scale service, and the front-end resource information of the operation request includes an IP address of the operation request.
In the embodiment of the invention, the gray request refers to a request for obtaining a corresponding target gray service from a client belonging to a gray object list.
In the embodiment of the present invention, the receiving, by the gateway based on Spring Cloud Gateway, an operation request includes:
acquiring a Maven configuration file, and adding a Spring Cloud Gateway gateway and corresponding dependency items of a pre-constructed Netty framework into the Maven configuration file to obtain Netty dependency;
And creating HTTP by taking the Netty framework as a bottom layer, monitoring and receiving an operation request by utilizing the HTTP based on Netty dependence.
The Maven is a construction tool for managing the dependency, compiling, testing and compressing tasks of the Java items, and the properties and the dependency of the service items are defined by a pon.xml configuration file of the Maven. Wherein the pon.xml configuration file refers to the project object model.
The Netty framework is an interpretable network application framework with value-open sources for rapidly developing high-performance network servers and clients.
In the embodiment of the invention, the Netty dependency refers to the correlation dependency between the Spring Cloud Gateway gateway and the Netty framework.
In the embodiment of the invention, the IP address of the operation request is extracted from the front-end resource information of the operation request;
acquiring configuration information of a gray object list, and extracting an IP address of the gray object list from the configuration information of an initial gray user list;
and extracting the operation request which is the same as the IP address of the gray object list from the operation request according to the IP address of the gray object list and the IP address of the operation request to obtain the gray request.
The configuration information of the gray scale user list may include an IP address of the gray scale object list.
S6, acquiring version information of the gray request, and in the gray release version, routing the gray request to the target gray service according to the version information of the gray request and a gateway routing rule, and operating the target gray service to obtain gray request feedback, wherein the gray request feedback is obtained by the target gray service, and the gray version number and the URL path of the gray request are the same.
The gray request version information includes gray request gray version number and URL path, and the gray request feedback is the result of running the target gray service same as the gray request gray version number and URL path.
In the embodiment of the present invention, in the gray release version, the method routes the gray request to the target gray service according to the version information of the gray request and the gateway routing rule, and operates the target gray service to obtain the gray request feedback, including:
creating Gateway configuration classes, and configuring Gateway routing rules into the Spring Cloud Gateway Gateway by using the Gateway configuration classes to obtain target routing rules;
extracting a version number and a URL path of the gray request from the version information of the gray request, and taking the version number of the gray request as a request interface of the Spring Cloud Gateway gateway;
Matching target gray scale service with the same gray scale version number and the same URI path with the gray scale request according to a request interface of the Spring Cloud Gateway gateway and a target routing rule;
according to the target routing rule, utilizing a Spring Cloud Gateway gateway to route the gray request to the target gray service;
and operating the target gray service according to the gray request to obtain gray request feedback.
And S7, adjusting target gray scale service according to the gray scale request feedback, updating a gray scale object list, and finishing gray scale release based on a micro-service architecture.
In the embodiment of the present invention, the adjusting the target gray scale service according to the gray scale request feedback, updating the gray scale object list, and completing the gray scale release based on the micro service architecture includes:
judging whether the target gray service with the same gray version number and the same URI path as the gray request is available service or not according to gray service feedback by utilizing Nacos;
if the target gray service is not available service, adjusting the target gray service by Nacos, and returning to the step of judging whether the target gray service with the same gray version number and the same URI path as the gray request is available service according to the gray service target;
If the target gray scale service is available service, acquiring a configuration file of a gray scale object list, and expanding a service object of the target gray scale service by using the configuration file of the gray scale object list to obtain a service user list;
and expanding the range of gray release versions according to the service user list, and realizing gray release based on the micro-service architecture.
Compared with the background art, the method comprises the following steps: according to the embodiment of the invention, an initial gray service, a gray front end and a gray object influenced by the gray release version are designated by configuring the gray release version, so that a gray object list is obtained by summarizing the gray object, a gray version number of a target gray service is designated by Nocas, a version routing rule is configured according to the gray version number of the gray service, a local routing rule is updated by Nacos, so as to obtain a gateway routing rule, an operation request of a client is received, a gray request is screened according to the gray object list, the gray request is routed by using a Spring Cloud Gateway gateway, the target gray service is operated, gray request feedback is obtained, the availability of the target gray service is judged according to the gray request feedback, the gray object list is updated, and gray release is realized. Therefore, the gray level release method, the gray level release device and the electronic equipment based on the micro-service architecture can solve the problems that the operation and maintenance cost is high and the gray level user group cannot be flexibly configured when gray level release is realized through the Nginx load balancing algorithm currently.
Example 2: fig. 2 is a functional block diagram of a gray scale distribution device based on a micro-service architecture according to an embodiment of the present invention.
The gray scale distribution device 100 based on the micro-service architecture can be installed in an electronic device. The gray scale distribution device 100 based on the micro-service architecture may include a gray scale distribution version configuration module 101, a gateway routing module 102, and a gray scale distribution version release module 103 according to the implemented functions. The module of the invention, which may also be referred to as a unit, refers to a series of computer program segments, which are stored in the memory of the electronic device, capable of being executed by the processor of the electronic device and of performing a fixed function.
The gray release version configuration module 101 is configured to designate an initial gray service and a gray front end of gray release according to a preset gray release plan, and configure a gray release version by using the initial gray service and the gray front end; acquiring configuration information of a gray level front end, and designating a service object of gray level release according to the configuration information of the gray level front end to obtain a gray level object list; registering the initial gray scale service into Nacos to obtain a target gray scale service, acquiring a configuration file of the Nacos, and designating a gray scale version number of the target gray scale service by using the configuration file of the Nacos; the obtaining the configuration file of the Nacos, and designating the gray scale version number of the target gray scale service by using the configuration file of the Nacos comprises the following steps: receiving a configuration file acquisition instruction, and constructing a secure connection with a pre-constructed Nacos configuration service; extracting identification information of a target gray scale service from the configuration file acquisition instruction, and acquiring a configuration file of Nacos according to the identification information; analyzing the configuration file of the Nacos to obtain configuration information related to the target gray scale service; identifying a gray scale version number of the target gray scale service from the configuration information;
The gateway routing module 102 is configured to obtain configuration information and a local routing rule of a target gray scale service, configure a version routing rule by using the configuration information and a gray scale version number of the target gray scale service, and dynamically and synchronously update the local routing rule according to the version routing rule to obtain a gateway routing rule; based on Spring Cloud Gateway gateway receiving operation request, obtaining front end resource information of the operation request, screening the operation request according to the front end resource information of the operation request and the gray object list, and obtaining gray request; the method comprises the steps of obtaining version information of a gray request, routing the gray request to a target gray service according to the version information of the gray request and a gateway routing rule in a gray release version, and operating the target gray service to obtain gray request feedback, wherein the target gray service is identical to a gray version number and a URL path of the gray request;
the gray release version release module 103 is configured to adjust a target gray service according to the gray request feedback, update a gray object list, and complete gray release based on a micro service architecture.
In detail, the modules in the gray level distribution device 100 based on the micro service architecture in the embodiment of the present invention use the same technical means as the gray level distribution method based on the micro service architecture described in fig. 1, and can generate the same technical effects, which is not described herein.
Example 3: fig. 3 is a schematic structural diagram of an electronic device for implementing a gray level distribution method based on a micro-service architecture according to an embodiment of the present invention.
The electronic device 1 may comprise a processor 10, a memory 11, a bus 12 and a communication interface 13, and may further comprise a computer program stored in the memory 11 and executable on the processor 10, such as a greyscale distribution program based on a micro-service architecture.
The processor 10 may be comprised of integrated circuits in some embodiments, for example, a single packaged integrated circuit, or may be comprised of multiple integrated circuits packaged with the same or different functions, including one or more central processing units (Central Processing unit, CPU), microprocessors, digital processing chips, graphics processors, combinations of various control chips, and the like. The processor 10 is a Control Unit (Control Unit) of the electronic device, connects respective components of the entire electronic device using various interfaces and lines, executes or executes programs or modules (for example, gradation release programs based on a micro-service architecture, etc.) stored in the memory 11, and invokes data stored in the memory 11 to perform various functions of the electronic device 1 and process the data.
The bus may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus, among others. The bus may be classified as an address bus, a data bus, a control bus, etc. The bus is arranged to enable a connection communication between the memory 11 and at least one processor 10 etc.
Fig. 3 shows only an electronic device with components, it being understood by a person skilled in the art that the structure shown in fig. 3 does not constitute a limitation of the electronic device 1, and may comprise fewer or more components than shown, or may combine certain components, or may be arranged in different components.
For example, although not shown, the electronic device 1 may further include a power source (such as a battery) for supplying power to each component, and preferably, the power source may be logically connected to the at least one processor 10 through a power management device, so that functions of charge management, discharge management, power consumption management, and the like are implemented through the power management device. The power supply may also include one or more of any of a direct current or alternating current power supply, recharging device, power failure detection circuit, power converter or inverter, power status indicator, etc. The electronic device 1 may further include various sensors, bluetooth modules, wi-Fi modules, etc., which will not be described herein.
Further, the electronic device 1 may also comprise a network interface, optionally the network interface may comprise a wired interface and/or a wireless interface (e.g. WI-FI interface, bluetooth interface, etc.), typically used for establishing a communication connection between the electronic device 1 and other electronic devices.
The electronic device 1 may optionally further comprise a user interface, which may be a Display, an input unit, such as a Keyboard (Keyboard), or a standard wired interface, a wireless interface. Alternatively, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch, or the like. The display may also be referred to as a display screen or display unit, as appropriate, for displaying information processed in the electronic device 1 and for displaying a visual user interface.
It should be understood that the embodiments described are for illustrative purposes only and are not limited to this configuration in the scope of the patent application.
The gray level distribution program based on the micro-service architecture stored in the memory 11 of the electronic device 1 is a combination of a plurality of instructions, which when executed in the processor 10, can implement:
Designating an initial gray scale service and a gray scale front end of gray scale release according to a preset gray scale release plan, and configuring a gray scale release version by utilizing the initial gray scale service and the gray scale front end;
acquiring configuration information of a gray level front end, and designating a service object of gray level release according to the configuration information of the gray level front end to obtain a gray level object list;
registering the initial gray scale service into Nacos to obtain a target gray scale service, acquiring a configuration file of the Nacos, and designating a gray scale version number of the target gray scale service by using the configuration file of the Nacos; the obtaining the configuration file of the Nacos, and designating the gray scale version number of the target gray scale service by using the configuration file of the Nacos comprises the following steps:
receiving a configuration file acquisition instruction, and constructing a secure connection with a pre-constructed Nacos configuration service;
extracting identification information of a target gray scale service from the configuration file acquisition instruction, and acquiring a configuration file of Nacos according to the identification information;
analyzing the configuration file of the Nacos to obtain configuration information related to the target gray scale service;
identifying a gray scale version number of the target gray scale service from the configuration information;
acquiring configuration information and local routing rules of a target gray scale service, configuring version routing rules by using the configuration information and gray scale version number of the target gray scale service, and dynamically and synchronously updating the local routing rules according to the version routing rules to obtain gateway routing rules;
Based on Spring Cloud Gateway gateway receiving operation request, obtaining front end resource information of the operation request, screening the operation request according to the front end resource information of the operation request and the gray object list, and obtaining gray request;
the method comprises the steps of obtaining version information of a gray request, routing the gray request to a target gray service according to the version information of the gray request and a gateway routing rule in a gray release version, and operating the target gray service to obtain gray request feedback, wherein the target gray service is identical to a gray version number and a URL path of the gray request;
and feeding back and adjusting the target gray scale service according to the gray scale request, updating a gray scale object list, and finishing gray scale release based on a micro-service architecture.
Specifically, the specific implementation method of the above instruction by the processor 10 may refer to descriptions of related steps in the corresponding embodiments of fig. 1 to 2, which are not repeated herein.
In the several embodiments provided in the present invention, it should be understood that the disclosed apparatus, device and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is merely a logical function division, and there may be other manners of division when actually implemented.
The modules described as separate components may or may not be physically separate, and components shown as modules may or may not be physical units, may be located in one place, or may be distributed over multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional module in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units can be realized in a form of hardware or a form of hardware and a form of software functional modules.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof.
Finally, it should be noted that the above-mentioned embodiments are merely for illustrating the technical solution of the present invention and not for limiting the same, and although the present invention has been described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications and equivalents may be made to the technical solution of the present invention without departing from the spirit and scope of the technical solution of the present invention.
Claims (6)
1. A gray level publishing method based on a micro-service architecture, the method comprising:
designating an initial gray scale service and a gray scale front end of gray scale release according to a preset gray scale release plan, and configuring a gray scale release version by utilizing the initial gray scale service and the gray scale front end;
acquiring configuration information of a gray level front end, and designating a service object of gray level release according to the configuration information of the gray level front end to obtain a gray level object list;
registering the initial gray scale service into Nacos to obtain a target gray scale service, acquiring a configuration file of the Nacos, and designating a gray scale version number of the target gray scale service by using the configuration file of the Nacos;
the obtaining the configuration file of the Nacos, and designating the gray scale version number of the target gray scale service by using the configuration file of the Nacos comprises the following steps:
receiving a configuration file acquisition instruction, and constructing a secure connection with a pre-constructed Nacos configuration service;
extracting identification information of a target gray scale service from the configuration file acquisition instruction, and acquiring a configuration file of Nacos according to the identification information;
analyzing the configuration file of the Nacos to obtain configuration information related to the target gray scale service;
identifying a gray scale version number of the target gray scale service from the configuration information;
Acquiring configuration information and local routing rules of a target gray scale service, configuring version routing rules by using the configuration information and gray scale version number of the target gray scale service, and dynamically and synchronously updating the local routing rules according to the version routing rules to obtain gateway routing rules;
based on Spring Cloud Gateway gateway receiving operation request, obtaining front end resource information of the operation request, screening the operation request according to the front end resource information of the operation request and the gray object list, and obtaining gray request;
the method comprises the steps of obtaining version information of a gray request, routing the gray request to a target gray service according to the version information of the gray request and a gateway routing rule in a gray release version, and operating the target gray service to obtain gray request feedback, wherein the target gray service is identical to a gray version number and a URL path of the gray request;
according to the gray request feedback, adjusting target gray service, updating a gray object list, and finishing gray release based on a micro-service architecture;
the service object of the gray level release is specified according to the configuration information of the gray level front end, and a gray level object list is obtained, which comprises the following steps:
extracting the IP address of the gray level front end from the configuration information of the gray level front end to obtain a target gray level IP address;
Acquiring a service object with the target gray IP address, and designating the service object as a gray object;
summarizing the gray objects to obtain a gray object list;
the configuring version routing rule by using the configuration information and the gray version number of the target gray service dynamically and synchronously updates the local routing rule according to the version routing rule to obtain a gateway routing rule, which comprises the following steps:
extracting a gray scale version number and a URL path of the target gray scale service from the configuration information of the target gray scale service;
creating a routing configuration space according to the gray version number of the target gray service and the URL path, setting the gray version number as an interface of the routing configuration space, and matching the target gray service with the same gray version number and URL path with the interface of the routing configuration space in the routing configuration space to obtain a version routing rule for routing the target gray service by using the gray version number and the URL path;
synchronously updating the version routing rule into the local routing rule by using Nacos to obtain a gateway routing rule;
the method for routing the gray request to the target gray service according to the version information of the gray request and the gateway routing rule, and operating the target gray service to obtain gray request feedback comprises the following steps:
Creating Gateway configuration classes, and configuring Gateway routing rules into the Spring Cloud Gateway Gateway by using the Gateway configuration classes to obtain target routing rules;
extracting a version number and a URL path of the gray request from the version information of the gray request, and taking the version number of the gray request as a request interface of the Spring Cloud Gateway gateway;
matching target gray scale service with the same gray scale version number and the same URL path with gray scale request according to a request interface and a target routing rule of the Spring Cloud Gateway gateway;
according to the target routing rule, utilizing a Spring Cloud Gateway gateway to route the gray request to the target gray service;
operating the target gray service according to the gray request to obtain gray request feedback;
the adjusting the target gray scale service according to the gray scale request feedback, updating the gray scale object list, completing the gray scale release based on the micro service architecture, comprising:
judging whether the target gray service with the same gray version number and the same URL path as the gray request is available service or not according to gray service feedback by utilizing Nacos;
if the target gray scale service is not available service, adjusting the target gray scale service by using Nacos, returning to the step of using Nacos, and judging whether the target gray scale service with the same gray scale version number and the same URL path as the gray scale request is available service according to gray scale service feedback;
If the target gray scale service is available service, acquiring a configuration file of a gray scale object list, and expanding a service object of the target gray scale service by using the configuration file of the gray scale object list to obtain a service user list;
and expanding the range of gray release versions according to the service user list, and realizing gray release based on the micro-service architecture.
2. The gray scale distribution method based on the micro service architecture according to claim 1, wherein the configuring the gray scale distribution version using the initial gray scale service and the gray scale front end comprises:
creating an initial gray scale environment, and introducing the initial gray scale service and the gray scale front end into the initial gray scale environment to obtain a target gray scale environment;
and putting the target gray environment into a pre-constructed service platform to obtain a gray release version.
3. The gray scale distribution method based on micro service architecture according to claim 1, wherein registering the initial gray scale service into the Nacos to obtain the target gray scale service comprises:
acquiring service information of an initial gray scale service, creating an initial Servicelnstance instance, and configuring the service information of the initial gray scale service in the initial Servicelnstance instance to obtain a target Servicelnstance instance;
Adding a Nacos Client SDK, and initializing Nacos configuration by using the Nacos Client SDK to obtain initial Nacos configuration;
the initial Nacos are utilized to configure a port of the designated Nacos, and a gray service registration port is obtained;
calling a registerlnstance method preset in a Nacos Client SDK according to a target Servicelstance instance, and registering an initial gray service in the Nacos by using the registerlnstance method and a gray service registration port to obtain a target gray service.
4. The gray scale distribution method based on micro service architecture according to claim 1, wherein the receiving the operation request based on the Spring Cloud Gateway gateway comprises:
acquiring a Maven configuration file, and adding a Spring Cloud Gateway gateway and corresponding dependency items of a pre-constructed Netty framework into the Maven configuration file to obtain Netty dependency;
and creating HTTP by taking the Netty framework as a bottom layer, monitoring and receiving an operation request by utilizing the HTTP based on Netty dependence.
5. The gray scale distribution method based on the micro service architecture according to claim 1, wherein the step of obtaining the gray scale request according to the front end resource information of the operation request and the gray scale object list filtering operation request comprises the steps of:
Extracting the IP address of the operation request from the front-end resource information of the operation request;
acquiring configuration information of a gray object list, and extracting an IP address of the gray object list from the configuration information of an initial gray user list; and extracting the operation request which is the same as the IP address of the gray object list from the operation request according to the IP address of the gray object list and the IP address of the operation request to obtain the gray request.
6. A micro-service architecture-based gray scale distribution device for implementing the micro-service architecture-based gray scale distribution method according to any one of claims 1 to 5, wherein the device comprises:
the gray release version configuration module is used for designating an initial gray service and a gray front end of gray release according to a preset gray release plan and configuring a gray release version by utilizing the initial gray service and the gray front end; acquiring configuration information of a gray level front end, and designating a service object of gray level release according to the configuration information of the gray level front end to obtain a gray level object list; registering the initial gray scale service into Nacos to obtain a target gray scale service, acquiring a configuration file of the Nacos, and designating a gray scale version number of the target gray scale service by using the configuration file of the Nacos; the obtaining the configuration file of the Nacos, and designating the gray scale version number of the target gray scale service by using the configuration file of the Nacos comprises the following steps: receiving a configuration file acquisition instruction, and constructing a secure connection with a pre-constructed Nacos configuration service; extracting identification information of a target gray scale service from the configuration file acquisition instruction, and acquiring a configuration file of Nacos according to the identification information; analyzing the configuration file of the Nacos to obtain configuration information related to the target gray scale service; identifying a gray scale version number of the target gray scale service from the configuration information;
The gateway routing module is used for acquiring configuration information and local routing rules of the target gray scale service, configuring version routing rules by utilizing the configuration information and gray scale version number of the target gray scale service, and dynamically and synchronously updating the local routing rules according to the version routing rules to obtain gateway routing rules; based on Spring Cloud Gateway gateway receiving operation request, obtaining front end resource information of the operation request, screening the operation request according to the front end resource information of the operation request and the gray object list, and obtaining gray request; the method comprises the steps of obtaining version information of a gray request, routing the gray request to a target gray service according to the version information of the gray request and a gateway routing rule in a gray release version, and operating the target gray service to obtain gray request feedback, wherein the target gray service is identical to a gray version number and a URL path of the gray request;
and the gray release version release module is used for feeding back and adjusting the target gray service according to the gray request, updating the gray object list and completing gray release based on the micro service architecture.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311443111.5A CN117170718B (en) | 2023-11-02 | 2023-11-02 | Gray scale release method and device based on micro-service architecture and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311443111.5A CN117170718B (en) | 2023-11-02 | 2023-11-02 | Gray scale release method and device based on micro-service architecture and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117170718A CN117170718A (en) | 2023-12-05 |
| CN117170718B true CN117170718B (en) | 2024-02-02 |
Family
ID=88947125
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311443111.5A Active CN117170718B (en) | 2023-11-02 | 2023-11-02 | Gray scale release method and device based on micro-service architecture and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117170718B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020181684A1 (en) * | 2019-03-12 | 2020-09-17 | 平安科技（深圳）有限公司 | Grayscale release management method, system and device, and storage medium |
| CN112000348A (en) * | 2020-07-28 | 2020-11-27 | 金蝶医疗软件科技有限公司 | Control method and device for service gray release and computer equipment |
| WO2021136233A1 (en) * | 2019-12-31 | 2021-07-08 | 华为技术有限公司 | Service upgrading method, device and system |
| CN113301161A (en) * | 2021-05-28 | 2021-08-24 | 平安科技（深圳）有限公司 | Seamless upgrading method, device, equipment and storage medium of application service |
| CN114040024A (en) * | 2020-07-20 | 2022-02-11 | 深圳兆日科技股份有限公司 | Gateway-based microservice grayscale publishing method, device, device and storage medium |
| WO2022267677A1 (en) * | 2021-06-22 | 2022-12-29 | 康键信息技术（深圳）有限公司 | Version updating method, apparatus, and device based on entire site grayscale, and storage medium |
| CN115665162A (en) * | 2022-10-26 | 2023-01-31 | 广州明动软件股份有限公司 | Intelligent shunting engine for gray scale release |
| CN116048835A (en) * | 2022-12-02 | 2023-05-02 | 上海通联金融服务有限公司 | SOFARPC-based high-availability remote service calling method for lifting core system |
| CN116483425A (en) * | 2023-04-07 | 2023-07-25 | 平安健康保险股份有限公司 | Micro-service gray level edition issuing method, device, equipment and storage medium thereof |
-
2023
- 2023-11-02 CN CN202311443111.5A patent/CN117170718B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020181684A1 (en) * | 2019-03-12 | 2020-09-17 | 平安科技（深圳）有限公司 | Grayscale release management method, system and device, and storage medium |
| WO2021136233A1 (en) * | 2019-12-31 | 2021-07-08 | 华为技术有限公司 | Service upgrading method, device and system |
| CN114040024A (en) * | 2020-07-20 | 2022-02-11 | 深圳兆日科技股份有限公司 | Gateway-based microservice grayscale publishing method, device, device and storage medium |
| CN112000348A (en) * | 2020-07-28 | 2020-11-27 | 金蝶医疗软件科技有限公司 | Control method and device for service gray release and computer equipment |
| CN113301161A (en) * | 2021-05-28 | 2021-08-24 | 平安科技（深圳）有限公司 | Seamless upgrading method, device, equipment and storage medium of application service |
| WO2022267677A1 (en) * | 2021-06-22 | 2022-12-29 | 康键信息技术（深圳）有限公司 | Version updating method, apparatus, and device based on entire site grayscale, and storage medium |
| CN115665162A (en) * | 2022-10-26 | 2023-01-31 | 广州明动软件股份有限公司 | Intelligent shunting engine for gray scale release |
| CN116048835A (en) * | 2022-12-02 | 2023-05-02 | 上海通联金融服务有限公司 | SOFARPC-based high-availability remote service calling method for lifting core system |
| CN116483425A (en) * | 2023-04-07 | 2023-07-25 | 平安健康保险股份有限公司 | Micro-service gray level edition issuing method, device, equipment and storage medium thereof |
Non-Patent Citations (1)
| Title |
|---|
| 电子银行系统灰度发布的研究与实现;李晓毅;;金融电子化(第01期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117170718A (en) | 2023-12-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2018200011B2 (en) | Systems and methods for blueprint-based cloud management | |
| CN109714449B (en) | Dynamic configuration method, device, equipment and storage medium for service domain name | |
| CA2937863C (en) | Method and system for comparing different versions of a cloud based application in a production environment using segregated backend systems | |
| US20190319885A1 (en) | Policy based service routing | |
| US11640289B2 (en) | Microservices cloud-native architecture for ubiquitous simulation as a service | |
| US20180225095A1 (en) | Application analyzer for cloud computing | |
| US10171294B2 (en) | Information processing device and system design support method | |
| CN106464529A (en) | Techniques to isolate a portion of an online computing service | |
| CN112506559B (en) | Gray release method and device based on gateway, electronic equipment and storage medium | |
| US11394750B1 (en) | System and method for generating network security policies in a distributed computation system utilizing containers | |
| EP3596600A1 (en) | Systems and methods for compute node management protocols | |
| CN113542387B (en) | System release method and device, electronic equipment and storage medium | |
| CN113312148B (en) | Big data service deployment method, device, equipment and medium | |
| CN107329827A (en) | Support lvs dispatching methods, equipment and the storage medium of Hash scheduling strategy | |
| CN117170718B (en) | Gray scale release method and device based on micro-service architecture and electronic equipment | |
| CN114827161A (en) | Service calling request sending method and device, electronic equipment and readable storage medium | |
| US10652283B1 (en) | Deriving system architecture from security group relationships | |
| US20250077551A1 (en) | Providing integration with a large language model for a network device | |
| CN115190076B (en) | Traffic diversion method, device, computer-readable storage medium, and electronic device | |
| CN115086321B (en) | Multi-cluster traffic forwarding method and device and electronic equipment | |
| CN111600749B (en) | Method and system for managing multiple servers and computer storage medium | |
| US10180830B2 (en) | Information processing device, deployment method, and recording medium | |
| CN114253525B (en) | Lightweight component bus implementation method, device, electronic device and medium | |
| CN117527880B (en) | Message management method, device, electronic equipment and computer readable storage medium | |
| CN119556944A (en) | A multi-microservice multi-environment deployment method, device, equipment, medium and product |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right |
Denomination of invention: A grayscale publishing method, device, and electronic device based on microservices architecture Granted publication date: 20240202 Pledgee: Guotou Taikang Trust Co.,Ltd. Pledgor: Green City Technology Industry Service Group Co.,Ltd. Registration number: Y2024980011350 |
|
| PE01 | Entry into force of the registration of the contract for pledge of patent right | ||
| PC01 | Cancellation of the registration of the contract for pledge of patent right |
Granted publication date: 20240202 Pledgee: Guotou Taikang Trust Co.,Ltd. Pledgor: Green City Technology Industry Service Group Co.,Ltd. Registration number: Y2024980011350 |
|
| PC01 | Cancellation of the registration of the contract for pledge of patent right |