CN112000348A - Control method and device for service gray release and computer equipment - Google Patents
Control method and device for service gray release and computer equipment Download PDFInfo
- Publication number
- CN112000348A CN112000348A CN202010735313.7A CN202010735313A CN112000348A CN 112000348 A CN112000348 A CN 112000348A CN 202010735313 A CN202010735313 A CN 202010735313A CN 112000348 A CN112000348 A CN 112000348A
- Authority
- CN
- China
- Prior art keywords
- service
- configuration information
- client
- version
- identifier
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 62
- 238000012545 processing Methods 0.000 claims abstract description 24
- 230000006870 function Effects 0.000 claims description 22
- 230000004048 modification Effects 0.000 claims description 19
- 238000012986 modification Methods 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 12
- 230000008859 change Effects 0.000 abstract description 6
- 230000008569 process Effects 0.000 description 17
- 238000010586 diagram Methods 0.000 description 6
- 239000000047 product Substances 0.000 description 4
- 238000012360 testing method Methods 0.000 description 4
- 238000007726 management method Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000008676 import Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000007704 transition Effects 0.000 description 2
- 241000287127 Passeridae Species 0.000 description 1
- 239000006227 byproduct Substances 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- PCHJSUWPFVWCPO-UHFFFAOYSA-N gold Chemical compound [Au] PCHJSUWPFVWCPO-UHFFFAOYSA-N 0.000 description 1
- 239000010931 gold Substances 0.000 description 1
- 229910052737 gold Inorganic materials 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000000116 mitigating effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application relates to a control method and device for service gray scale release, computer equipment and a storage medium. The method comprises the following steps: receiving a service request sent by a client through a gateway, wherein the service request comprises a service identifier and a version identifier; searching corresponding routing configuration information according to the service identifier and the version identifier; sending the routing configuration information to the gateway, and sending the service request to a corresponding target service instance through the gateway according to the routing configuration information; and processing the service request by using the target service instance to obtain a result corresponding to the service request and returning the result to the client. By adopting the method, the calling link for dynamically customizing the service gray level release based on different service scenes can be realized, the path change of the access service version is realized, the complicated operations such as restarting, loading and configuring are avoided, the stability of the service system during updating and iteration can be ensured, and the efficiency of the service gray level release is effectively improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for controlling service gray level publishing, a computer device, and a storage medium.
Background
With the development of computer technology and the coming of the 5G era, the appearance of the Internet brings great convenience to modern life, more and more enterprises can process various services on line by using a service platform, and the service handling efficiency is effectively improved. In the micro-service architecture of the existing service system, when a new version of a micro-service instance needs to be released, gray release can provide effective guarantee for fast iterative micro-service, and the user range influenced by product upgrading is reduced.
In the existing method for issuing the micro-service in the gray scale, when a new version needs to be issued to the instances in the micro-service cluster, all the service instances of the whole service link need to be redeployed, corresponding configurations need to be manually updated in the proxy server and the service gateway, and the updating is realized by reloading the corresponding configurations.
Disclosure of Invention
In view of the above, it is necessary to provide a method, an apparatus, a computer device, and a storage medium for controlling service gray scale distribution, which can improve service gray scale distribution efficiency.
A control method of service gray publication, the method comprising:
receiving a service request sent by a client through a gateway, wherein the service request comprises a service identifier and a version identifier;
searching corresponding routing configuration information according to the service identifier and the version identifier;
sending the routing configuration information to the gateway, and sending the service request to a corresponding target service instance through the gateway according to the routing configuration information;
and processing the service request by using the target service instance to obtain a result corresponding to the service request and returning the result to the client.
In one embodiment, before receiving the service request sent by the client through the gateway, the method further includes:
receiving a resource acquisition request sent by the client in a polling mode;
acquiring updated service version information corresponding to the modification operation;
and returning the service version information to the client according to the resource acquisition request, so that the client updates metadata in a memory according to the service version information and calls the updated service version.
In one embodiment, before receiving the service request sent by the client through the gateway, the method further includes:
receiving a resource acquisition request sent by the client in a polling mode;
acquiring updated route configuration information corresponding to the modification operation;
according to the resource acquisition request, returning the routing configuration information to the client and storing the routing configuration information locally at the client; and the routing configuration information is used for indicating the client to call the corresponding service instance according to the routing configuration information.
In one embodiment, before receiving a service request sent by a client through a gateway or after obtaining a result corresponding to the service request and returning the result to the client, the method further includes:
receiving a resource acquisition request sent by the client in a polling mode;
acquiring updated service configuration information corresponding to the modification operation; the service configuration information comprises calling relations among services;
and returning the service configuration information to the client according to the resource acquisition request, so that the client updates the metadata in the memory according to the service configuration information and calls the corresponding service instance according to the updated calling relationship between the services.
In one embodiment, the service configuration information includes a logic function corresponding to the target service identifier and the target version identifier calling link information;
the processing the service request by using the target service instance comprises:
receiving a parameter acquisition request sent by the target service instance according to the service request, wherein the parameter acquisition request comprises the access parameter;
when the input part and the input part are matched with the logic function, service instance information corresponding to the calling link information is searched according to the logic function, wherein the service instance information comprises a service instance identifier and a service instance version identifier;
and sending the service instance information to the target service instance so that the target service instance calls the corresponding service instance according to the service instance information.
In one embodiment, the service configuration information further includes weight proportion data corresponding to each version identifier corresponding to the service identifier; and the weight proportion data is used for distributing client access flow corresponding to each version identifier according to the service request sent by the client and the weight proportion data.
In one embodiment, the searching for the corresponding routing configuration information according to the service identifier and the version identifier includes:
according to the service identification and the version identification, searching whether a configuration center has routing configuration information corresponding to the service identification and the version identification;
the sending the routing configuration information to the gateway includes:
if the configuration center has the routing configuration information corresponding to the service identifier and the version identifier, sending the routing configuration information to the gateway;
if the configuration center does not have the routing configuration information corresponding to the service identifier and the version identifier, the routing configuration information carried in the service request is obtained, and the routing configuration information is sent to the gateway.
A control apparatus for service gray scale distribution, the apparatus comprising:
the receiving module is used for receiving a service request sent by a client through a gateway, wherein the service request comprises a service identifier and a version identifier;
the searching module is used for searching corresponding routing configuration information according to the service identifier and the version identifier;
the sending module is used for sending the routing configuration information to the gateway and sending the service request to a corresponding target service instance through the gateway according to the routing configuration information;
and the processing module is used for processing the service request by using the target service instance, obtaining a result corresponding to the service request and returning the result to the client.
A computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:
receiving a service request sent by a client through a gateway, wherein the service request comprises a service identifier and a version identifier;
searching corresponding routing configuration information according to the service identifier and the version identifier;
sending the routing configuration information to the gateway, and sending the service request to a corresponding target service instance through the gateway according to the routing configuration information;
and processing the service request by using the target service instance to obtain a result corresponding to the service request and returning the result to the client.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
receiving a service request sent by a client through a gateway, wherein the service request comprises a service identifier and a version identifier;
searching corresponding routing configuration information according to the service identifier and the version identifier;
sending the routing configuration information to the gateway, and sending the service request to a corresponding target service instance through the gateway according to the routing configuration information;
and the target service instance is used for processing the service request, obtaining a result corresponding to the service request and returning the result to the client.
The control method, the control device, the computer equipment and the storage medium for the service gray scale release receive a service request sent by a client through a gateway, wherein the service request comprises a service identifier and a version identifier. The server searches corresponding routing configuration information according to the service identifier and the version identifier, sends the routing configuration information to the gateway, and sends a service request to a corresponding target service instance through the gateway according to the routing configuration information. The service request can be processed by using the target service instance, and the obtained result corresponding to the service request is returned to the client. Therefore, when a new version of the service instance under the micro-service cluster needs to be released, the calling link for dynamically customizing the service gray release based on different service scenes can be realized only by changing the routing configuration information in the configuration center of the server, so that the path change of accessing the service version is realized, a series of complicated operations such as restarting and loading the service configuration are avoided, the stability of the service system during updating iteration can be ensured, and the efficiency of releasing the service gray is effectively improved.
Drawings
FIG. 1 is a diagram illustrating an exemplary embodiment of a control method for gray-scale service distribution;
FIG. 2 is a flow chart illustrating a control method for service gray scale distribution according to an embodiment;
FIG. 3 is a flowchart illustrating steps for obtaining updated service version information corresponding to a modify operation in one embodiment;
FIG. 4 is a flowchart illustrating steps for obtaining updated routing configuration information corresponding to a modify operation in one embodiment;
FIG. 5 is a flowchart illustrating steps for obtaining updated service configuration information corresponding to a modify operation in one embodiment;
fig. 6A is a flowchart illustrating a control method for service gray scale distribution in another embodiment;
FIG. 6B is a timing diagram of service gray scale release control in one embodiment;
FIG. 7 is a flowchart illustrating the steps of searching for corresponding routing configuration information according to a service identifier and a version identifier in an embodiment;
FIG. 8 is a block diagram showing the construction of a control device for serving gradation issuance in one embodiment;
FIG. 9 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The control method for service gray scale release provided by the application can be applied to the application environment shown in fig. 1. Wherein the client 102 communicates with the server 104 over a network. The client 102 may obtain the service processing data corresponding to the service request from the server 104 by sending the service request to the server 104. The server 104 receives a service request sent by the client 102 through the gateway, where the service request includes a service identifier and a version identifier. The server 104 searches for corresponding routing configuration information according to the service identifier and the version identifier. The server 104 sends the routing configuration information to the gateway, and sends the service request to the corresponding target service instance through the gateway according to the routing configuration information. The server 104 processes the service request by using the target service instance, and the server 104 obtains a result corresponding to the service request and returns the result to the client 102. The client 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented by an independent server or a server cluster composed of a plurality of servers.
In one embodiment, as shown in fig. 2, a method for controlling service gray scale distribution is provided, which is described by taking the method as an example applied to the server in fig. 1, and includes the following steps:
The terminal is a kind of embedded computer system equipment, and the software structure can be divided into system software and application software. In the software structure of the terminal, the system software mainly includes an operating system and middleware, and the common terminal operating systems include apple IOS, google Android, hewlett packard WebOS, open source MeeGo, microsoft Windows, and the like. In the application software of the terminal, developers can adopt the micro-service architecture to create applications with different service functions around the service field components, the applications can be independently developed, managed and updated, and the micro-service cloud architecture and the platform are used in the dispersed components, so that the deployment, management and service function delivery become simpler. The currently commonly used micro-service frameworks are mainly Spring Cloud and Dubbo (or DubboX). The micro-service framework of Spring Cloud can be used in this application. Microservice is an emerging software architecture that can split a large single application and service into tens of supporting microservices. The strategy of microservices can make work easier, it can extend a single component rather than the entire application stack, to meet service level agreements. Users using different operating system terminal devices can download various types of application programs through the application market interface in the terminal, wherein the application programs can include system application programs, desktop application programs, driving application programs, network application programs, internet of things application programs and the like. The application programs can also comprise an instant messaging application program, an online shopping application program, a video and audio entertainment application program and the like from different business function divisions of the application programs used by users. When the service is released to be on-line or the application of the server side needs to be upgraded in the existing system, a gray release service mode can be adopted. Gray scale distribution (aka gold sparrow distribution) refers to a distribution method that can smoothly transition between black and white. In the quick iteration process of the service version, the gray version and the formal version can coexist, and the gray version is gradually released to the upgraded formal version, so that the service does not need to be stopped for a period of time in the release process of the service updating version, the transition process among different versions can be monitored, and once the problem of the gray version is found, the state of the original formal version can be quickly returned.
Specifically, a user may log in a service system in a specific scenario by inputting a user name and a password in a mobile phone Application program or a browser webpage, the user may initiate a specific service request through an app (Application) client or a web client, that is, a web browser, and a server may receive the service request sent by the client through a gateway, where the service request includes a service identifier and a version identifier. The client, which is referred to as a user side, refers to a program corresponding to the server and providing local services to the client. Except for some application programs which only run locally, the application programs are generally installed on common clients and need to be operated together with a server. The clients may include DNS clients, web clients, game clients, mobile clients, and the like. For example, the mobile client is a mobile phone, and the mobile client is software that can run on a mobile phone terminal. The service request refers to a service request which is initiated by a user in different service scene systems according to different requirements and corresponds to a service function. The gateway is a service gateway for providing a uniform service entrance, the service gateway may include a Zuul gateway, and Zuul is a micro service API gateway in a Spring Cloud micro service framework. For example, in an online shopping application, a user may initiate a create order request through a trigger operation and send it to a server through a service gateway. When the server receives an order creating request sent by the client through the service gateway, the server can obtain a currently available service list from the service registration center according to the service identifier and the version identifier in the order creating request, and call the corresponding service instance. The server can be pre-deployed with a service registry and a service configuration center, all services are registered in the service registry, and simultaneously, a currently available service list can be obtained from the service registry. The service configuration center is used for uniformly managing all services in the service system. For example, the Nacos is a new open source project, the core location of the Nacos is a dynamic service discovery, configuration and service management platform which is easier to help build a cloud native application, and a developer can dynamically update a configuration mechanism by modifying configuration information in the Nacos. The service identifier is used for identifying a unique service, the version identifier refers to different version information corresponding to the same service issued by adopting gray scale in a service system, and the version information can comprise a formal version and a gray scale version. For example, the created micro-Service in a certain shopping application is an Order Service, i.e., "Order Service", and developers may continuously optimize the function of updating the Order Service, and may release an updated grayscale version of the Order Service 1.1 version and the Order Service 1.2 version, etc. in the Service system.
And step 204, searching corresponding routing configuration information according to the service identifier and the version identifier.
After the server receives the service request sent by the client through the gateway, the server can search the routing configuration information corresponding to the service called by the service request from the service configuration center according to the service identifier and the version identifier corresponding to the service request. The routing configuration information refers to path information for invoking services, that is, full link information configured by a service according to an invoking sequence between services. The routing configuration information may include call link information between services. For example, after the server receives an order request sent by the client through the gateway, the server may search, from the service configuration center, routing configuration information corresponding to the invoked service according to the service identifier and the version identifier corresponding to the order request. Suppose an order is created, during which the data in the "Customer service and the data in the" Product service need to be read. The server searches that the path configuration information corresponding to the calling Service is the calling Order Service' according to the Order creating request sent by the client, and the Order Service also needs to call customer Service and product Service when processing the Service request sent by the client, namely the Order Service obtains corresponding data in the customer Service and the product Service by calling the customer Service and the product Service. The service configuration center may preset routing configuration information corresponding to a service called by a certain service request, for example, in a configuration interface of the service configuration center, a developer may preset a corresponding routing rule or may also input configuration information: service: route: version { guide-svc-a:1.0, guide-svc-B:1.1}, when the server receives the service request sent by the client through the service gateway, the server can find that the route configuration information corresponding to the service called by the service request sent by the client is SvcA1.0 → SvcB1.1 according to the service identifier and the version identifier, namely, the service gateway forwards the service request to the service A for processing, when the service A processes the service request, the service A also needs to call the 1.1 version of the service B, and the service B1.1 version is a gray version.
After the server searches the corresponding routing configuration information according to the service identifier and the version identifier, the server sends the searched routing configuration information to the service gateway, and sends a service request to the corresponding target service instance through the service gateway according to the routing configuration information. The target service instance refers to one of the service instances selected according to the preset routing rule or the routing configuration information from the plurality of service instances as the target service instance, for example, the service instance corresponding to the service B may include a formal version of the service B1.0 and a grayscale version of the service B1.1. In addition, when the daily access volume of a Web service system is gradually increased from 10 ten thousand to 1000 ten thousand, a service request sent by a client can be forwarded to a corresponding target server address by deploying software with a load balancing function or module and the like. Load balancing is one of the important means for high availability of the system, mitigation of network pressure, and capacity expansion of processing capacity. Load balancing refers to load balancing of a server, and is divided into hardware load balancing and software load balancing. The hardware load balancing is mainly realized by devices specially used for load balancing among server nodes, and the software load balancing is realized by installing some software for load balancing functions or modules on the server to complete the request distribution work, for example, Nginx (engine x) is a high-performance HTTP and reverse proxy web server, the number of running copies of a new version and an old version can be quickly adjusted through Nginx, and meanwhile, the traffic can be led to the new version according to percentage. In addition, individual user traffic can be specified to the new version by matching HTTP headers. For example, a client may invoke a service in an http request manner, and after receiving a service request sent by the client, the nginn, that is, the reverse proxy web server obtains one server address corresponding to an available service from a maintained available server list according to a preset configuration rule or algorithm (for example, linear polling, load by weight, load by traffic, and the like), and forwards the service request sent by the client to the server address.
And step 208, processing the service request by using the target service instance, obtaining a result corresponding to the service request and returning the result to the client.
And after the server sends the searched routing configuration information to the service gateway and sends the service request to the corresponding target service instance according to the routing configuration information through the service gateway, the server processes the service request by using the target service instance to obtain a result corresponding to the service request and returns the result to the client. When the target service instance processes the service request sent by the client, other services may be invoked at the same time. For example, after the user selects a commodity in the shopping interface, the user clicks a button to pay "Checkout" and generates a corresponding Order "," Checkout "and" Order "which are all constructed microservices. The calling between the services can be completed in an RPC mode and an event notification mode. When the "Order" service processes a service request sent by a client, the "Order" service also needs to call several other services to assist in completing the whole function. And after the 'Checkout' service is finished, sending an 'Order' message, receiving Payment of a user after the 'Payment' service receives the message, sending a 'Payment received' message, namely, processing the service request of the client by calling other services through the 'Order' service, finishing the service request for receiving the collection and ordering, and returning a processing result corresponding to the service request to the corresponding client.
In a traditional gray scale publishing service mode, configuration needs to be changed in a secondary load (namely nginx server cluster) of a system, relevant configuration is downloaded, secondary distribution needs to be carried out through a gateway, and a service calling request is routed to a downstream service. When the system relates to gray level service, no matter whether the upstream and downstream services are gray level or not, the whole calling service link is required to be reset to release a new instance, and version routing between the services cannot be realized.
In this embodiment, a service request sent by a client through a gateway is received, where the service request includes a service identifier and a version identifier. The server searches corresponding routing configuration information according to the service identifier and the version identifier, sends the routing configuration information to the gateway, and sends a service request to a corresponding target service instance through the gateway according to the routing configuration information. The service request can be processed by using the target service instance, and the obtained result corresponding to the service request is returned to the client. Therefore, when a new version needs to be released to an instance under the micro-service cluster, the calling link for dynamically customizing the micro-service gray release based on different service scene characteristics can be realized only by changing the routing configuration information in the configuration center of the server, the path change for accessing the micro-service version is achieved, the complex operations such as loading service restarting and the like are not needed, the stability of the system during updating iteration can be ensured, and meanwhile, the service gray release efficiency is effectively improved.
In an embodiment, as shown in fig. 3, before receiving a service request sent by a client through a gateway, the method further includes a step of obtaining updated service version information corresponding to the modification operation, which specifically includes:
And step 304, acquiring updated service version information corresponding to the modification operation.
Before the server receives a service request sent by the client through the gateway, if a developer needs to update a service in a certain service system and release gray-scale services, the developer can update version information corresponding to different services in a service configuration center interface deployed on the server. Specifically, the server may receive a resource acquisition request sent by the client in a polling manner, and the client may send an http request at regular time by using a short polling manner. The client can also send a request to the server by adopting a long polling mode, namely the client sends the request to the server until receiving a message returned by the server or the client continues to send the next request after the request is overtime. For example, for a certain instant messaging application, a developer updates the grayscale version a1.2 corresponding to the service a in the service configuration center interface, and the developer may input configuration information as: cloud: noncos, discovery, metadata, version, 1.2. When the server receives a resource acquisition request sent by the client in a polling manner, the server can acquire that the updated service version information corresponding to the modification operation of the developer is A1.2, and then the server returns the updated service version information to the corresponding client according to the resource acquisition request sent by the client, so that the client updates metadata in the memory according to the updated service version information and calls the updated service version, namely the A1.2 version of the updated service A. Therefore, the micro-service version can be dynamically changed, the micro-service loading and updating configuration does not need to be restarted, the configuration does not need to be changed in the nginx server cluster, the second distribution is carried out through the gateway, a series of complex operations that the whole calling service link corresponding to one service is reset and released and the like are avoided, the path for accessing the service version can be changed directly by changing the service version, and the service gray level releasing efficiency is effectively improved.
In an embodiment, as shown in fig. 4, before receiving a service request sent by a client through a gateway, the method further includes a step of obtaining updated routing configuration information corresponding to the modification operation, which specifically includes:
And step 406, returning the routing configuration information to the client according to the resource acquisition request, and storing the routing configuration information in the local area of the client, where the routing configuration information is used to instruct the client to call the corresponding service instance according to the routing configuration information.
Before the server receives a service request sent by a client through a gateway, after the gray scale service is released, a tester can set that a new version application is started first, but not all user traffic is directly led in, but the tester tests the new version on line, if the new version application has no problem in operation, a developer can lead in a small amount of user traffic to the new version, namely the developer can change link information of a small amount of user calling service, the developer can continue to observe the operation state of the new version, collect data in various operation processes, and compare various data of the new version with various data of the old version to perform A/B test. After the new version is confirmed to operate well, more traffic is led into the new version step by step, and in the period, the number of copies of the servers of the new version and the old version which operate can be continuously adjusted, so that the new version can bear more and more traffic pressure until 100% of traffic is switched to the new version, and finally the rest of old version service is closed, and the gray release is completed. Specifically, after the developer confirms that the new version of the grayscale release operates well, the developer can gradually introduce more traffic into the new version, that is, the developer modifies part of the user side in the service configuration center interface to call the service of the new version, and the developer can input configuration information as follows: account: route: { mwp-token:1.1} accountIds: FD80DE, AE 587. when the server receives the resource acquisition request sent by the client in the polling mode, for example, the client can acquire updated configuration data by sending an http request, the server can acquire updated route configuration information corresponding to the modification operation input by the developer. And the server returns the routing configuration information to the client according to the received resource acquisition request sent by the client and stores the routing configuration information in the local part of the client. When the client initiates the service request next time, the client can call the corresponding service instance according to the updated routing configuration information stored in the local, that is, the routing configuration information corresponding to the client calling service is changed from the original 1.0 version of the service a to the 1.1 version of the service a, wherein svca1.1 is the gray level version of the service a. Therefore, if a new version is found to have problems in the gray release process (gray period), each service requests to acquire real-time updated configuration information in a polling mode through a dynamic real-time updating configuration mechanism, the traffic can be dynamically switched back to the old version without taking the link service of the whole service off line, the negative influence of the gray release can be controlled in the minimum range, the stability of the service system during update iteration is ensured, and the efficiency of the gray release is effectively improved.
In an embodiment, as shown in fig. 5, before receiving a service request sent by a client through a gateway or after obtaining a result corresponding to the service request and returning the result to the client, the method further includes a step of obtaining updated service configuration information corresponding to the modification operation, which specifically includes:
Before the server receives the service request sent by the client through the gateway or after the server returns the result corresponding to the service request sent by the client last time to the client, the developer can also modify the configuration information corresponding to each service in the service configuration center interface, wherein the service configuration information comprises the calling relationship among the services. For example, the configuration item corresponding to the a1.0 version of the current service a is svca1.0 → svcb1.0, i.e. the calling relationship between the services is that the service a1.0 calls the service B1.0. After the developer confirms that the B1.1 version of the new version service B released in grayscale operates well, the developer can modify the configuration item corresponding to the service a in the service configuration center interface, that is, the developer can modify the call relationship between the service a and other services in the service configuration center interface, and the developer can input configuration information as follows: service: route { guide-svc-a:1.0, guide-svc-b:1.1}, when the server receives a resource acquisition request sent by the client in a polling manner, the server can acquire updated service configuration information corresponding to the modification operation input by the developer. And the server returns the updated service configuration information to the client according to the received resource acquisition request sent by the client, so that the client updates the metadata in the memory according to the updated service configuration information. When the client initiates the same service request next time, the service a1.0 may call the corresponding service instance B1.1 according to the updated routing configuration information, that is, the routing configuration information corresponding to the a service is changed from original svca1.0 → svcb1.0 to svca1.0 → svcb1.1, where svcb1.1 is a grayscale version of the service B. Therefore, under the characteristics of the service scene, the gray control under different service scenes is realized by modifying the configuration information corresponding to the service A and calling the configuration information of the corresponding relation of a certain version of service through the pushing service A, when the routing relation among the services needs to be changed, the updated configuration information is pushed again by changing the service configuration information, the stability of the service system during updating iteration can be ensured, and meanwhile, the efficiency of service gray release is effectively improved.
In one embodiment, as shown in fig. 6A, a method for controlling service gray scale distribution is provided, which is described by taking the method as an example applied to the server in fig. 1, and includes the following steps:
And step 610, when the participating logic functions are matched, searching and calling corresponding service instance information in the link information according to the logic functions, wherein the service instance information comprises service instance identification and service instance version identification.
When a developer needs to update the service a and the service B in the existing service system and release the grayscale service, the developer can update version information and service configuration information corresponding to the service a and the service B in a service configuration center interface deployed on a server. After the grayscale versions of the service A and the service B are released, a tester needs to perform online testing on the new versions corresponding to the service A and the service B, if the application of the new versions runs without problems, a developer can introduce a small amount of user traffic into the new versions, that is, the developer can change link information of a small amount of users calling the service, and can continue to observe the running state of the new versions and collect data during running. And after the tester confirms that the new version operates well, introducing more flow into the new version step by step. Specifically, as shown in fig. 6B, a timing chart of service gray scale release control in a certain service scenario is provided. The developer can directly update new versions corresponding to the service a and the service B to be svca1.1 and svcb1.1 in the service configuration center interface, and modify configuration information corresponding to the service a, and the developer can input the configuration information in the service configuration center interface as follows: service: route { guide-svc-a:1.1, guide-svc-B:1.1}, namely, the route configuration information corresponding to the service A is changed from original SvcA1.0 → SvcB1.0 to SvcA1.1 → SvcB1.1, wherein SvcA1.1 is the gray scale version of the service A, and SvcB1.1 is the gray scale version of the service B.
When the server receives a service request sent by the client through the gateway, the server searches corresponding route configuration information from the service configuration center according to the service identifier and the version identifier in the service request, wherein the route configuration information is SvcA1.1 → SvcB1.1. The server sends the routing configuration information to the service gateway, and sends a service request to the corresponding target service instance SvcA1.1 through the service gateway according to the routing configuration information. When the target service instance svca1.1 receives the service request sent by the client, the service svca1.1 processes the service request. In the process of processing the service svca1.1, the service svca1.1 may send a parameter acquisition request corresponding to the service request to the server, and the server receives the parameter acquisition request sent by the service svca1.1 according to the service request, where the parameter acquisition request includes the entry parameter. The server searches a logic function matched with the access parameter from the service configuration center, and when the server searches the logic function matched with the access parameter, the server searches service instance information contained in the service A calling link information according to the matched logic function, wherein the service instance information comprises a service instance identifier and a service instance version identifier. That is, the server searches for service instance information corresponding to the service a call link information as svcb1.1 according to the matched logic function, and then sends the service instance information svcb1.1 to the service svca1.1, so that the service svca1.1 calls a service request sent by the service svcb1.1 to cooperatively process the service request, after the service request is processed by the service svca1.1 and the service svcb1.1, a result corresponding to the service request is obtained, and the server returns the service processing result to the corresponding client. Therefore, the calling link for dynamically customizing the gray release of the micro-service based on different service scene characteristics can be realized, the change of the path for accessing the micro-service version is realized, a series of complicated operations such as restarting and loading service configuration are not required to be avoided, the stability of the service system during updating and iteration can be ensured, and the efficiency of the gray release of the service is effectively improved.
In one embodiment, the service configuration information further includes weight proportion data corresponding to each version identifier corresponding to the service identifier, and the weight proportion data is used for allocating client access traffic corresponding to each version identifier according to a service request sent by the client and according to the weight proportion data. Specifically, after the gray scale service is released, the developer does not directly import all the access traffic of the client, but the tester performs online test on the new version of the gray scale release, and after the developer confirms that the new version of the gray scale release operates well, the developer needs to gradually import more traffic to the new version. During the period, the developer can also continuously adjust the number of the running server copies of the new version and the old version so that the new version can bear greater and greater traffic pressure until 100% of traffic is switched to the new version, and finally, the service of the remaining old version is closed, and the gray release is completed. Therefore, the developer can also modify the weight proportion data in each service configuration information in the service configuration center, namely, distributing different flow proportions to different versions of service instances. For example, the developer may modify the weight proportion data of different versions corresponding to the service a and the service B, that is, the developer may set a corresponding routing rule in the service configuration center interface or input configuration information as: service: route: { guide-svc-a:1.0 ═ 90; 2.0-10, guide-svc-b: 1.0-80; 2.0 ═ 20}, i.e., version 1.0 and version 1.1 of service a, accounting for 90% and 10% of the total traffic, respectively; version 1.0 and version 1.1 of service B account for 80% and 20% of the total traffic, respectively. In addition, different versions of traffic distribution work may also be done by software or modules with load balancing functionality, such as a Nginx proxy server. Therefore, in the gray level control scene of the multi-version service, the weight (flow proportion) is distributed to the services of different versions according to different requirements, so that the flow of the service A accessing the service B can be dynamically allocated between the version B1.0 and the version B1.1, the stability of the service system during updating iteration can be ensured, and the efficiency of service gray level release can be effectively improved.
In one embodiment, as shown in fig. 7, the step of searching for corresponding routing configuration information according to the service identifier and the version identifier includes:
After the server receives the service request sent by the client through the gateway, the server can search the routing configuration information corresponding to the service request according to the service identifier and the version identifier in the service request. Specifically, the server may search, according to the service identifier and the version identifier in the service request, whether the configuration center has the routing configuration information corresponding to the service identifier and the version identifier. If the configuration center has the routing configuration information corresponding to the service identifier and the version identifier, the server sends the routing configuration information to the gateway, the gateway can store the routing configuration information in the local of the gateway, when the same service request sent by the client is received next time, the gateway does not need to acquire the corresponding routing configuration information from the service configuration center, and the gateway can directly forward the service request sent by the client to the corresponding service instance for processing according to the routing configuration information stored in the local, so that the complicated flow of request interaction can be effectively reduced. If the server does not find the routing configuration information corresponding to the service identifier and the version identifier in the configuration center, the server can acquire the routing configuration information carried in the service request sent by the client, and the server sends the routing configuration information carried in the http request sent by the client to the gateway. The client can obtain the result of the service processing in the http request mode, and can add the routing rule parameter or carry the relevant service version information in the request header, namely the header of the http. For example, an addHeader method may be used to set key to the service name and value to the version, such as: addHeader ("svc-a", "1.0"). Therefore, in the gray level control scene of the multi-version service, the route configuration information changed by the configuration center is preferentially acquired, so that the unified management of all services can be ensured, if the configuration center cannot read the corresponding configuration, the setting can be carried out according to the header parameter of the client, the stability of the service system during updating iteration can be ensured, and meanwhile, the efficiency of service gray level release is effectively improved.
It should be understood that although the various steps in the flow charts of fig. 1-7 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 1-7 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.
In one embodiment, as shown in fig. 8, there is provided a control apparatus for service gray scale distribution, including: a receiving module 802, a searching module 804, a sending module 806, and a processing module 808, wherein:
the receiving module 802 is configured to receive a service request sent by a client through a gateway, where the service request includes a service identifier and a version identifier.
The searching module 804 is configured to search for corresponding routing configuration information according to the service identifier and the version identifier.
The sending module 806 is configured to send the routing configuration information to the gateway, and send the service request to the corresponding target service instance through the gateway according to the routing configuration information.
And the processing module 808 is configured to process the service request by using the target service instance, obtain a result corresponding to the service request, and return the result to the client.
In one embodiment, the apparatus further comprises: the device comprises an acquisition module and a return module.
The receiving module is also used for receiving the resource acquisition request sent by the client in a polling mode. The obtaining module is used for obtaining the updated service version information corresponding to the modification operation. The return module is used for returning the service version information to the client according to the resource acquisition request, so that the client updates the metadata in the memory according to the service version information and calls the updated service version.
In one embodiment, the apparatus further comprises: and a storage module.
The receiving module is also used for receiving the resource acquisition request sent by the client in a polling mode. The obtaining module is further configured to obtain updated routing configuration information corresponding to the modification operation. The storage module is used for returning the routing configuration information to the client according to the resource acquisition request and storing the routing configuration information in the local part of the client, and the routing configuration information is used for indicating the client to call the corresponding service instance according to the routing configuration information.
In one embodiment, the receiving module is further configured to receive a resource acquisition request sent by the client in a polling manner. The obtaining module is further configured to obtain updated service configuration information corresponding to the modification operation, where the service configuration information includes a call relationship between services. The return module is further used for returning the service configuration information to the client according to the resource acquisition request, so that the client updates the metadata in the memory according to the service configuration information and calls the corresponding service instance according to the updated calling relationship between the services.
In one embodiment, the apparatus further comprises: and a searching module.
The receiving module is further configured to receive a parameter obtaining request sent by the target service instance according to the service request, where the parameter obtaining request includes the access parameter. And the searching module is used for searching corresponding service instance information in the calling link information according to the logic function when the participating logic function is matched, wherein the service instance information comprises a service instance identifier and a service instance version identifier. The sending module is further used for sending the service instance information to the target service instance, so that the target service instance calls the corresponding service instance according to the service instance information.
In one embodiment, the apparatus further comprises: and a distribution module.
And the distribution module is used for distributing client access flow corresponding to each version identifier according to the service request sent by the client and the weight proportion data.
In one embodiment, the searching module is further configured to search, according to the service identifier and the version identifier, whether the configuration center has routing configuration information corresponding to the service identifier and the version identifier; if the configuration center has the routing configuration information corresponding to the service identifier and the version identifier, the routing configuration information is sent to the gateway; and if the configuration center does not have the routing configuration information corresponding to the service identifier and the version identifier, acquiring the routing configuration information carried in the service request, and sending the routing configuration information to the gateway.
For specific definition of the control device for service gray scale distribution, reference may be made to the above definition of the control method for service gray scale distribution, and details are not described herein again. The modules in the control device for service gray scale distribution can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 9. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing routing configuration data for calling service gray scale distribution. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a control method for service gray scale distribution.
Those skilled in the art will appreciate that the architecture shown in fig. 9 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the steps of the above-described method embodiments being implemented when the computer program is executed by the processor.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A control method of service gray publication, the method comprising:
receiving a service request sent by a client through a gateway, wherein the service request comprises a service identifier and a version identifier;
searching corresponding routing configuration information according to the service identifier and the version identifier;
sending the routing configuration information to the gateway, and sending the service request to a corresponding target service instance through the gateway according to the routing configuration information;
and processing the service request by using the target service instance to obtain a result corresponding to the service request and returning the result to the client.
2. The method of claim 1, wherein before receiving the service request sent by the client through the gateway, the method further comprises:
receiving a resource acquisition request sent by the client in a polling mode;
acquiring updated service version information corresponding to the modification operation;
and returning the service version information to the client according to the resource acquisition request, so that the client updates metadata in a memory according to the service version information and calls the updated service version.
3. The method of claim 1, wherein before receiving the service request sent by the client through the gateway, the method further comprises:
receiving a resource acquisition request sent by the client in a polling mode;
acquiring updated route configuration information corresponding to the modification operation;
according to the resource acquisition request, returning the routing configuration information to the client and storing the routing configuration information locally at the client; and the routing configuration information is used for indicating the client to call the corresponding service instance according to the routing configuration information.
4. The method according to claim 1, wherein before receiving the service request sent by the client through the gateway or after obtaining a result corresponding to the service request and returning the result to the client, the method further comprises:
receiving a resource acquisition request sent by the client in a polling mode;
acquiring updated service configuration information corresponding to the modification operation; the service configuration information comprises calling relations among services;
and returning the service configuration information to the client according to the resource acquisition request, so that the client updates the metadata in the memory according to the service configuration information and calls the corresponding service instance according to the updated calling relationship between the services.
5. The method of claim 4, wherein the service configuration information comprises a logical function corresponding to target service identification and target version identification call link information;
the processing the service request by using the target service instance comprises:
receiving a parameter acquisition request sent by the target service instance according to the service request, wherein the parameter acquisition request comprises the access parameter;
when the input part and the input part are matched with the logic function, service instance information corresponding to the calling link information is searched according to the logic function, wherein the service instance information comprises a service instance identifier and a service instance version identifier;
and sending the service instance information to the target service instance so that the target service instance calls the corresponding service instance according to the service instance information.
6. The method of claim 5, wherein the service configuration information further comprises weight ratio data corresponding to each version identifier corresponding to a service identifier; and the weight proportion data is used for distributing client access flow corresponding to each version identifier according to the service request sent by the client and the weight proportion data.
7. The method of claim 1, wherein the searching for the corresponding routing configuration information according to the service identifier and the version identifier comprises:
according to the service identification and the version identification, searching whether a configuration center has routing configuration information corresponding to the service identification and the version identification;
the sending the routing configuration information to the gateway includes:
if the configuration center has the routing configuration information corresponding to the service identifier and the version identifier, sending the routing configuration information to the gateway;
if the configuration center does not have the routing configuration information corresponding to the service identifier and the version identifier, the routing configuration information carried in the service request is obtained, and the routing configuration information is sent to the gateway.
8. A control apparatus for service gray scale distribution, the apparatus comprising:
the receiving module is used for receiving a service request sent by a client through a gateway, wherein the service request comprises a service identifier and a version identifier;
the searching module is used for searching corresponding routing configuration information according to the service identifier and the version identifier;
the sending module is used for sending the routing configuration information to the gateway and sending the service request to a corresponding target service instance through the gateway according to the routing configuration information;
and the processing module is used for processing the service request by using the target service instance, obtaining a result corresponding to the service request and returning the result to the client.
9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010735313.7A CN112000348A (en) | 2020-07-28 | 2020-07-28 | Control method and device for service gray release and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010735313.7A CN112000348A (en) | 2020-07-28 | 2020-07-28 | Control method and device for service gray release and computer equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112000348A true CN112000348A (en) | 2020-11-27 |
Family
ID=73467897
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010735313.7A Pending CN112000348A (en) | 2020-07-28 | 2020-07-28 | Control method and device for service gray release and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112000348A (en) |
Cited By (36)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112202929A (en) * | 2020-12-01 | 2021-01-08 | 湖南新云网科技有限公司 | Service access method, device and equipment in micro-service architecture |
| CN112463251A (en) * | 2020-12-03 | 2021-03-09 | 中国建设银行股份有限公司 | Method and device for configuring hot publishing by uliweb framework |
| CN112506559A (en) * | 2020-12-14 | 2021-03-16 | 招商局金融科技有限公司 | Gray scale publishing method and device based on gateway, electronic equipment and storage medium |
| CN112565469A (en) * | 2021-02-23 | 2021-03-26 | 常州微亿智造科技有限公司 | Method for realizing dynamic gray strategy for micro-service and micro-service system |
| CN112632032A (en) * | 2020-12-18 | 2021-04-09 | 华人运通(上海)云计算科技有限公司 | Data migration method and device, storage medium and terminal equipment |
| CN112685075A (en) * | 2020-12-31 | 2021-04-20 | 五八有限公司 | Gray scale distribution method and device, electronic equipment and computer readable medium |
| CN112685287A (en) * | 2020-11-30 | 2021-04-20 | 青岛海尔科技有限公司 | Product data testing method and device, storage medium and electronic device |
| CN112737942A (en) * | 2020-12-24 | 2021-04-30 | 深圳市彬讯科技有限公司 | Service route switching method, device, equipment and medium |
| CN112764765A (en) * | 2021-01-21 | 2021-05-07 | 中信银行股份有限公司 | Application gray level publishing method and system and computer readable storage medium |
| CN112905210A (en) * | 2021-03-24 | 2021-06-04 | 青岛聚看云科技有限公司 | Server and gray scale publishing method |
| CN112995269A (en) * | 2020-12-10 | 2021-06-18 | 腾讯科技（深圳）有限公司 | Data processing method, computer device and readable storage medium |
| CN113254063A (en) * | 2021-06-30 | 2021-08-13 | 四川新网银行股份有限公司 | Gray level verification filter and filtering method |
| CN113282602A (en) * | 2021-06-18 | 2021-08-20 | 北京奇艺世纪科技有限公司 | Service request method and device |
| CN113301161A (en) * | 2021-05-28 | 2021-08-24 | 平安科技（深圳）有限公司 | Seamless upgrading method, device, equipment and storage medium of application service |
| CN113422732A (en) * | 2021-06-22 | 2021-09-21 | 康键信息技术（深圳）有限公司 | Version updating method, device, equipment and storage medium based on total station gray scale |
| CN113452776A (en) * | 2021-06-25 | 2021-09-28 | 中国工商银行股份有限公司 | PaaS platform service scheduling method and device and PaaS platform |
| CN113489788A (en) * | 2021-07-06 | 2021-10-08 | 广州华多网络科技有限公司 | Data routing control method, data analysis processing method, data routing control device, data analysis processing device and data analysis processing medium |
| CN113518119A (en) * | 2021-05-25 | 2021-10-19 | 深圳壹账通智能科技有限公司 | Service distribution method, device, equipment and storage medium of ABTest |
| CN113641400A (en) * | 2021-08-10 | 2021-11-12 | 广州鲁邦通智能科技有限公司 | Method for sharing micro-service public resource by multi-version service, API gateway and management system |
| CN113676549A (en) * | 2021-09-02 | 2021-11-19 | 京东科技信息技术有限公司 | Application request distribution method, application gateway, electronic device and storage medium |
| CN113791805A (en) * | 2021-09-17 | 2021-12-14 | 马上消费金融股份有限公司 | Micro-service gray level publishing method and device |
| CN113791799A (en) * | 2021-01-06 | 2021-12-14 | 北京沃东天骏信息技术有限公司 | System upgrading method and device, computer readable storage medium and electronic equipment |
| CN113992559A (en) * | 2021-11-01 | 2022-01-28 | 腾讯科技（深圳）有限公司 | Message processing method, device, equipment and computer readable storage medium |
| CN114138325A (en) * | 2021-11-24 | 2022-03-04 | 聚好看科技股份有限公司 | Gray scale publishing method and device |
| CN114153526A (en) * | 2021-12-01 | 2022-03-08 | 北京百度网讯科技有限公司 | Agent-based gray level configuration method, device, electronic device and medium |
| CN114338763A (en) * | 2021-12-20 | 2022-04-12 | 深圳Tcl新技术有限公司 | Micro-service calling method, device, server and computer readable storage medium |
| CN114422440A (en) * | 2022-03-28 | 2022-04-29 | 北京沃丰时代数据科技有限公司 | Gray scale distribution method and device, electronic equipment and storage medium |
| CN114650293A (en) * | 2020-12-17 | 2022-06-21 | 中移(苏州)软件技术有限公司 | Method, device, terminal and computer storage medium for flow distribution |
| CN114726919A (en) * | 2022-03-22 | 2022-07-08 | 新华三大数据技术有限公司 | Method and device for controlling gray level flow, computer equipment and storage medium |
| CN114827282A (en) * | 2022-03-30 | 2022-07-29 | 阿里云计算有限公司 | Service routing method, device, equipment and storage medium |
| CN115002227A (en) * | 2022-05-19 | 2022-09-02 | 青岛海尔科技有限公司 | User access request response method, storage medium and electronic device |
| CN115250233A (en) * | 2022-09-22 | 2022-10-28 | 中邮消费金融有限公司 | Gray scale routing control method, gray scale routing assembly and computer equipment |
| CN116319514A (en) * | 2023-05-22 | 2023-06-23 | 腾讯科技（深圳）有限公司 | Data processing method and related device |
| CN116594678A (en) * | 2023-07-18 | 2023-08-15 | 太平金融科技服务（上海）有限公司 | Development joint debugging isolation method, device, computer equipment and storage medium |
| CN116860381A (en) * | 2023-09-04 | 2023-10-10 | 厦门民航凯亚有限公司 | Method for releasing visual micro-service gray scale |
| CN117170718A (en) * | 2023-11-02 | 2023-12-05 | 绿城科技产业服务集团有限公司 | Gray scale release method and device based on micro-service architecture and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140282468A1 (en) * | 2013-03-15 | 2014-09-18 | Microsoft Corporation | Local store data versioning |
| CN105099988A (en) * | 2014-04-24 | 2015-11-25 | 阿里巴巴集团控股有限公司 | Method used for supporting gray releasing, access method, devices and system |
| WO2017071425A1 (en) * | 2015-10-29 | 2017-05-04 | 腾讯科技（深圳）有限公司 | Method and device for updating version |
| CN109739552A (en) * | 2019-01-04 | 2019-05-10 | 深圳壹账通智能科技有限公司 | Micro services gray scale dissemination method, device, computer equipment and storage medium |
-
2020
- 2020-07-28 CN CN202010735313.7A patent/CN112000348A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140282468A1 (en) * | 2013-03-15 | 2014-09-18 | Microsoft Corporation | Local store data versioning |
| CN105099988A (en) * | 2014-04-24 | 2015-11-25 | 阿里巴巴集团控股有限公司 | Method used for supporting gray releasing, access method, devices and system |
| WO2017071425A1 (en) * | 2015-10-29 | 2017-05-04 | 腾讯科技（深圳）有限公司 | Method and device for updating version |
| CN109739552A (en) * | 2019-01-04 | 2019-05-10 | 深圳壹账通智能科技有限公司 | Micro services gray scale dissemination method, device, computer equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 杨俊伟;纪鑫;胡强新;: "基于微服务架构的电力云服务平台", 电力信息与通信技术, no. 01, 15 January 2017 (2017-01-15) * |
Cited By (57)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112685287A (en) * | 2020-11-30 | 2021-04-20 | 青岛海尔科技有限公司 | Product data testing method and device, storage medium and electronic device |
| CN112685287B (en) * | 2020-11-30 | 2023-11-28 | 青岛海尔科技有限公司 | Product data testing method and device, storage medium and electronic device |
| CN112202929A (en) * | 2020-12-01 | 2021-01-08 | 湖南新云网科技有限公司 | Service access method, device and equipment in micro-service architecture |
| CN112202929B (en) * | 2020-12-01 | 2021-03-26 | 湖南新云网科技有限公司 | Service access method, device and equipment in micro-service architecture |
| CN112463251A (en) * | 2020-12-03 | 2021-03-09 | 中国建设银行股份有限公司 | Method and device for configuring hot publishing by uliweb framework |
| CN112995269B (en) * | 2020-12-10 | 2022-01-11 | 腾讯科技（深圳）有限公司 | Data processing method, computer device and readable storage medium |
| CN112995269A (en) * | 2020-12-10 | 2021-06-18 | 腾讯科技（深圳）有限公司 | Data processing method, computer device and readable storage medium |
| CN112506559B (en) * | 2020-12-14 | 2024-02-06 | 招商局金融科技有限公司 | Gray release method and device based on gateway, electronic equipment and storage medium |
| CN112506559A (en) * | 2020-12-14 | 2021-03-16 | 招商局金融科技有限公司 | Gray scale publishing method and device based on gateway, electronic equipment and storage medium |
| CN114650293A (en) * | 2020-12-17 | 2022-06-21 | 中移(苏州)软件技术有限公司 | Method, device, terminal and computer storage medium for flow distribution |
| CN114650293B (en) * | 2020-12-17 | 2024-02-23 | 中移(苏州)软件技术有限公司 | Method, device, terminal and computer storage medium for flow diversion |
| CN112632032A (en) * | 2020-12-18 | 2021-04-09 | 华人运通(上海)云计算科技有限公司 | Data migration method and device, storage medium and terminal equipment |
| CN112737942A (en) * | 2020-12-24 | 2021-04-30 | 深圳市彬讯科技有限公司 | Service route switching method, device, equipment and medium |
| CN112737942B (en) * | 2020-12-24 | 2022-06-03 | 土巴兔集团股份有限公司 | Service route switching method, device, equipment and medium |
| CN112685075A (en) * | 2020-12-31 | 2021-04-20 | 五八有限公司 | Gray scale distribution method and device, electronic equipment and computer readable medium |
| CN113791799A (en) * | 2021-01-06 | 2021-12-14 | 北京沃东天骏信息技术有限公司 | System upgrading method and device, computer readable storage medium and electronic equipment |
| CN112764765A (en) * | 2021-01-21 | 2021-05-07 | 中信银行股份有限公司 | Application gray level publishing method and system and computer readable storage medium |
| CN112565469A (en) * | 2021-02-23 | 2021-03-26 | 常州微亿智造科技有限公司 | Method for realizing dynamic gray strategy for micro-service and micro-service system |
| CN112905210A (en) * | 2021-03-24 | 2021-06-04 | 青岛聚看云科技有限公司 | Server and gray scale publishing method |
| CN112905210B (en) * | 2021-03-24 | 2023-09-15 | 青岛聚看云科技有限公司 | Server and gray level publishing method |
| CN113518119A (en) * | 2021-05-25 | 2021-10-19 | 深圳壹账通智能科技有限公司 | Service distribution method, device, equipment and storage medium of ABTest |
| CN113301161B (en) * | 2021-05-28 | 2023-02-03 | 平安科技（深圳）有限公司 | Seamless upgrading method, device, equipment and storage medium of application service |
| CN113301161A (en) * | 2021-05-28 | 2021-08-24 | 平安科技（深圳）有限公司 | Seamless upgrading method, device, equipment and storage medium of application service |
| CN113282602B (en) * | 2021-06-18 | 2023-10-27 | 北京奇艺世纪科技有限公司 | Service request method and device |
| CN113282602A (en) * | 2021-06-18 | 2021-08-20 | 北京奇艺世纪科技有限公司 | Service request method and device |
| WO2022267677A1 (en) * | 2021-06-22 | 2022-12-29 | 康键信息技术（深圳）有限公司 | Version updating method, apparatus, and device based on entire site grayscale, and storage medium |
| CN113422732A (en) * | 2021-06-22 | 2021-09-21 | 康键信息技术（深圳）有限公司 | Version updating method, device, equipment and storage medium based on total station gray scale |
| CN113452776B (en) * | 2021-06-25 | 2022-12-09 | 中国工商银行股份有限公司 | PaaS platform service scheduling method and device and PaaS platform |
| CN113452776A (en) * | 2021-06-25 | 2021-09-28 | 中国工商银行股份有限公司 | PaaS platform service scheduling method and device and PaaS platform |
| CN113254063B (en) * | 2021-06-30 | 2021-09-21 | 四川新网银行股份有限公司 | Gray level verification filter and filtering method |
| CN113254063A (en) * | 2021-06-30 | 2021-08-13 | 四川新网银行股份有限公司 | Gray level verification filter and filtering method |
| CN113489788B (en) * | 2021-07-06 | 2024-01-30 | 广州华多网络科技有限公司 | Data route control and data analysis processing method and device, equipment and medium |
| CN113489788A (en) * | 2021-07-06 | 2021-10-08 | 广州华多网络科技有限公司 | Data routing control method, data analysis processing method, data routing control device, data analysis processing device and data analysis processing medium |
| CN113641400A (en) * | 2021-08-10 | 2021-11-12 | 广州鲁邦通智能科技有限公司 | Method for sharing micro-service public resource by multi-version service, API gateway and management system |
| CN113676549A (en) * | 2021-09-02 | 2021-11-19 | 京东科技信息技术有限公司 | Application request distribution method, application gateway, electronic device and storage medium |
| CN113791805A (en) * | 2021-09-17 | 2021-12-14 | 马上消费金融股份有限公司 | Micro-service gray level publishing method and device |
| CN113992559B (en) * | 2021-11-01 | 2023-02-24 | 腾讯科技（深圳）有限公司 | Message processing method, device, equipment and computer readable storage medium |
| CN113992559A (en) * | 2021-11-01 | 2022-01-28 | 腾讯科技（深圳）有限公司 | Message processing method, device, equipment and computer readable storage medium |
| CN114138325A (en) * | 2021-11-24 | 2022-03-04 | 聚好看科技股份有限公司 | Gray scale publishing method and device |
| CN114153526A (en) * | 2021-12-01 | 2022-03-08 | 北京百度网讯科技有限公司 | Agent-based gray level configuration method, device, electronic device and medium |
| CN114338763A (en) * | 2021-12-20 | 2022-04-12 | 深圳Tcl新技术有限公司 | Micro-service calling method, device, server and computer readable storage medium |
| CN114338763B (en) * | 2021-12-20 | 2024-01-19 | 深圳Tcl新技术有限公司 | Micro-service calling method, micro-service calling device, server and computer readable storage medium |
| CN114726919A (en) * | 2022-03-22 | 2022-07-08 | 新华三大数据技术有限公司 | Method and device for controlling gray level flow, computer equipment and storage medium |
| CN114726919B (en) * | 2022-03-22 | 2024-02-13 | 新华三大数据技术有限公司 | Gray scale flow control method, device, computer equipment and storage medium |
| CN114422440A (en) * | 2022-03-28 | 2022-04-29 | 北京沃丰时代数据科技有限公司 | Gray scale distribution method and device, electronic equipment and storage medium |
| CN114827282A (en) * | 2022-03-30 | 2022-07-29 | 阿里云计算有限公司 | Service routing method, device, equipment and storage medium |
| CN115002227B (en) * | 2022-05-19 | 2024-03-22 | 青岛海尔科技有限公司 | User access request response method, storage medium and electronic device |
| CN115002227A (en) * | 2022-05-19 | 2022-09-02 | 青岛海尔科技有限公司 | User access request response method, storage medium and electronic device |
| CN115250233B (en) * | 2022-09-22 | 2022-12-16 | 中邮消费金融有限公司 | Gray scale routing control method, gray scale routing assembly and computer equipment |
| CN115250233A (en) * | 2022-09-22 | 2022-10-28 | 中邮消费金融有限公司 | Gray scale routing control method, gray scale routing assembly and computer equipment |
| CN116319514B (en) * | 2023-05-22 | 2023-08-08 | 腾讯科技（深圳）有限公司 | Data processing method and related device |
| CN116319514A (en) * | 2023-05-22 | 2023-06-23 | 腾讯科技（深圳）有限公司 | Data processing method and related device |
| CN116594678A (en) * | 2023-07-18 | 2023-08-15 | 太平金融科技服务（上海）有限公司 | Development joint debugging isolation method, device, computer equipment and storage medium |
| CN116860381A (en) * | 2023-09-04 | 2023-10-10 | 厦门民航凯亚有限公司 | Method for releasing visual micro-service gray scale |
| CN116860381B (en) * | 2023-09-04 | 2023-11-28 | 厦门民航凯亚有限公司 | Method for releasing visual micro-service gray scale |
| CN117170718B (en) * | 2023-11-02 | 2024-02-02 | 绿城科技产业服务集团有限公司 | Gray scale release method and device based on micro-service architecture and electronic equipment |
| CN117170718A (en) * | 2023-11-02 | 2023-12-05 | 绿城科技产业服务集团有限公司 | Gray scale release method and device based on micro-service architecture and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112000348A (en) | Control method and device for service gray release and computer equipment | |
| CN112118565B (en) | Multi-tenant service gray level publishing method, device, computer equipment and storage medium | |
| US10776171B2 (en) | Endpoint management system and virtual compute system | |
| CN101571809B (en) | Implementation method of plug-in registration and device thereof | |
| US20040230670A1 (en) | Method and system for representing, configuring and deploying distributed applications | |
| CN108492005B (en) | Project data processing method and device, computer equipment and storage medium | |
| CN113055492A (en) | Control method and device for service gray scale link, computer equipment and storage medium | |
| CN110704177B (en) | Computing task processing method and device, computer equipment and storage medium | |
| CN103841134A (en) | API-based method for sending and receiving information, API-based apparatus, and API-based system | |
| CN110968331B (en) | Method and device for running application program | |
| US20170192765A1 (en) | Dynamic code component deployment in cloud-based service platforms | |
| CN112767135B (en) | Configuration method and device of rule engine, storage medium and computer equipment | |
| CN114615340B (en) | Request processing method and device, computer equipment and storage device | |
| CN112767133B (en) | Service decision method and device, storage medium and computer equipment | |
| CN112433863A (en) | Micro-service calling method and device, terminal equipment and storage medium | |
| CN111090423A (en) | Webhook framework system and method for realizing active calling and event triggering | |
| CN113656087A (en) | Applet starting method, device, equipment and storage medium | |
| US20210304068A1 (en) | Data processing system and data processing method | |
| US20200310828A1 (en) | Method, function manager and arrangement for handling function calls | |
| CN111694639A (en) | Method and device for updating address of process container and electronic equipment | |
| CN114385382A (en) | Light application access method and device, computer equipment and storage medium | |
| CN111913759B (en) | Method, apparatus, computing device and medium for controlling execution of application program | |
| CN113360210A (en) | Data reconciliation method and device, computer equipment and storage medium | |
| CN112232751A (en) | Service data processing method, device, system, computer equipment and storage medium | |
| CN115811481A (en) | Interactive service testing method and device, computer equipment and storage medium |
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 |