CN112118565A - Multi-tenant service gray level publishing method and device, computer equipment and storage medium - Google Patents
Multi-tenant service gray level publishing method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN112118565A CN112118565A CN202010817357.4A CN202010817357A CN112118565A CN 112118565 A CN112118565 A CN 112118565A CN 202010817357 A CN202010817357 A CN 202010817357A CN 112118565 A CN112118565 A CN 112118565A
- Authority
- CN
- China
- Prior art keywords
- service
- service instance
- tenant
- service request
- terminal
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 82
- 238000012545 processing Methods 0.000 claims abstract description 23
- 230000008569 process Effects 0.000 claims description 31
- 238000004590 computer program Methods 0.000 claims description 12
- 239000000284 extract Substances 0.000 claims description 6
- 230000006870 function Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 5
- 230000008520 organization Effects 0.000 description 4
- 235000006719 Cassia obtusifolia Nutrition 0.000 description 3
- 235000014552 Cassia tora Nutrition 0.000 description 3
- 244000201986 Cassia tora Species 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000002085 persistent effect Effects 0.000 description 3
- 239000000047 product Substances 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000007726 management method Methods 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
- 238000013461 design 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
- 230000010354 integration Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 230000000116 mitigating effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/183—Processing at user equipment or user record carrier
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/20—Transfer of user or subscriber data
- H04W8/205—Transfer to or from user equipment or user record carrier
-
- 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
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The application relates to a multi-tenant service gray level release method and device, computer equipment and a storage medium. The method comprises the following steps: receiving a service request sent by a terminal through a gateway, wherein the service request comprises a tenant identification; determining downstream service instance information corresponding to the tenant identification according to the tenant identification; if the downstream service instance information carries the label service instance information of the tenant identification, the service request is sent to the label service instance in the label service instance information; and processing the service request by using the label service instance to obtain a result corresponding to the service request and returning the result to the terminal. By adopting the method, the service request of the specific tenant can be routed to the specified service instance, a series of complicated operations such as restarting and loading service configuration are avoided, the stability of the service system during updating iteration can be ensured, and meanwhile, the multi-tenant service gray level publishing efficiency is effectively improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a multi-tenant service gray level publishing method, apparatus, computer device, and 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.
When the service gray scale release under a multi-tenant scene is involved, different tenants need to release service instances of different versions, and access of the different tenants needs to be isolated. However, in the current manner of issuing the micro-service in grayscale, when the grayscale is issued by using a routing manner of a client in a spring cloud architecture, even when multiple instances of different versions are deployed under the same service, requests sent by tenants are evenly distributed to the instances, and a service requirement that a specified service instance is routed according to tenant information and isolated for different tenants cannot be realized, so that the efficiency of issuing the grayscale of the multi-tenant service is easily low.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a multi-tenant service gray scale distribution method, apparatus, computer device, and storage medium capable of improving multi-tenant service gray scale distribution efficiency.
A multi-tenant service gray scale publishing method, the method comprising:
receiving a service request sent by a terminal through a gateway, wherein the service request comprises a tenant identification;
determining downstream service instance information corresponding to the tenant identification according to the tenant identification;
if the downstream service instance information carries the label service instance information of the tenant identification, the service request is sent to the label service instance in the label service instance information;
and processing the service request by using the label service instance to obtain a result corresponding to the service request and returning the result to the terminal.
In one embodiment, before the receiving the service request sent by the terminal through the gateway, the method further includes:
establishing a gray-scale service instance cluster in a configuration interface, and binding or deleting a specific tenant identification in the gray-scale service instance cluster to obtain updated configuration information;
receiving a resource acquisition request sent by the terminal in a polling mode;
and returning the updated configuration information to the terminal according to the resource acquisition request, wherein the updated configuration information is used for indicating the terminal to update the metadata in the memory and calling the gray level service instance in the updated configuration information.
In one embodiment, after receiving the service request sent by the terminal through the gateway, the method further includes:
and according to the tenant identification, if the downstream service instance information corresponding to the tenant identification does not exist in the searching process, the service request is sent to the corresponding non-gray level service instance according to the original routing strategy.
In one embodiment, after the step of sending the service request to the tag service instance in the tag service instance information if the downstream service instance information carries the tag service instance information of the tenant identity, the method further includes:
acquiring all tag service instance information lists carrying the tenant identification;
and calling the corresponding label service instance from the label service instance information list according to a preset weight proportion.
In one embodiment, the method further comprises:
and if the downstream service instance information does not carry the label service instance information of the tenant identification, sending the service request to a corresponding non-grayscale downstream service instance according to an original routing strategy.
In one embodiment, before the receiving the service request sent by the terminal through the gateway, the method further includes:
and configuring the attribute of the service request sent by the terminal in the basic data packet, so that the gateway extracts the corresponding tenant identification from the service request sent by the terminal, adds the tenant identification to the service request and forwards the tenant identification to the corresponding downstream service instance.
In one embodiment, the processing the service request by using the tag service instance includes:
in an asynchronous thread, when the tag service instance needs to call other service instances to process the service request, a tenant identification is preferentially obtained from a gateway thread; and the tenant identification is used for calling the service instance version matched with the tenant identification from the service instances of different versions corresponding to the same service when calling between the service instances.
A multi-tenant service gray scale issuing apparatus, the apparatus comprising:
the system comprises a receiving module, a sending module and a processing module, wherein the receiving module is used for receiving a service request sent by a terminal through a gateway, and the service request comprises a tenant identification;
the determining module is used for determining downstream service instance information corresponding to the tenant identification according to the tenant identification;
a sending module, configured to send the service request to a tag service instance in the tag service instance information if the downstream service instance information carries the tag service instance information of the tenant identifier;
and the processing module is used for processing the service request by using the label service instance, obtaining a result corresponding to the service request and returning the result to the terminal.
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 terminal through a gateway, wherein the service request comprises a tenant identification;
determining downstream service instance information corresponding to the tenant identification according to the tenant identification;
if the downstream service instance information carries the label service instance information of the tenant identification, the service request is sent to the label service instance in the label service instance information;
and processing the service request by using the label service instance to obtain a result corresponding to the service request and returning the result to the terminal.
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 terminal through a gateway, wherein the service request comprises a tenant identification;
determining downstream service instance information corresponding to the tenant identification according to the tenant identification;
if the downstream service instance information carries the label service instance information of the tenant identification, the service request is sent to the label service instance in the label service instance information;
and processing the service request by using the label service instance to obtain a result corresponding to the service request and returning the result to the terminal.
According to the multi-tenant service gray scale publishing method, device, computer equipment and storage medium, when the service gray scale publishing under a multi-tenant scene needs to be carried out on different tenants and different versions of service instances are published, a server receives a service request sent by a terminal through a gateway, and the service request comprises a tenant identification. And the server determines the downstream service instance information corresponding to the tenant identification according to the tenant identification. And if the server finds the tag service instance information of the tenant identification carried by the downstream service instance information, the server sends the service request to the tag service instance in the tag service instance information, processes the service request by using the tag service instance, obtains a result corresponding to the service request and returns the result to the terminal. Therefore, when different tenants need to be isolated and service instances of different versions are issued, the calling link for dynamically adjusting the service gray level issuance based on different service scenes can be realized only by changing the routing configuration information in the configuration center of the server and binding different tenants to different service clusters, so that the service request of a specific tenant is routed to the specified service instance, a series of complicated operations such as restarting and loading service configuration are avoided, the stability of the service system during updating iteration can be ensured, and the efficiency of the multi-tenant service gray level issuance is effectively improved.
Drawings
FIG. 1 is a diagram of an application environment of a multi-tenant service gray-scale publishing method in one embodiment;
FIG. 2 is a flowchart illustrating a multi-tenant service gray-scale publishing method in one embodiment;
FIG. 3 is a flowchart illustrating the steps of creating a gray scale service instance cluster in one embodiment;
fig. 4 is a schematic flowchart of a multi-tenant service gray-scale distribution method in another embodiment;
FIG. 5 is a block diagram of a multi-tenant service gray-scale distribution apparatus in one embodiment;
FIG. 6 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 multi-tenant service gray scale publishing method provided by the application can be applied to the application environment shown in fig. 1. Wherein the terminal 102 communicates with the server 104 via a network. The terminal 102 may obtain 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 terminal 102 through the gateway, where the service request includes a tenant identity. The server 104 determines the downstream service instance information corresponding to the tenant identification according to the tenant identification. If the server 104 detects that the downstream service instance information carries the tag service instance information of the tenant identifier, the server 104 sends the service request to the tag service instance in the tag service instance information. The server 104 processes the service request by using the tag service instance, obtains a result corresponding to the service request, and returns the result to the terminal 102. The terminal 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 formed by a plurality of servers.
In one embodiment, as shown in fig. 2, a multi-tenant service gray scale publishing method 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 microservice is a product under the SOA architecture, the design goal is to dismiss the business, so that the service can run independently, the strategy of microservice can make the work simpler, and the microservice can extend a single component rather than the whole application program stack, thereby meeting the service level agreement. 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 gray scale release, an A/B test can be performed, namely, a part of users continue to use the product characteristic A, a part of users start to use the product characteristic B, and if the users do not have any objection to the B, the range is gradually expanded, and all the users are migrated to the B. The stability of the whole system can be ensured by gray scale release, and problems can be found and adjusted in the initial gray scale so as to ensure the influence degree of the gray scale. 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 scene 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 a service request sent by a terminal through a gateway, where the service request includes a tenant identifier. The client, which is referred to as a user terminal, refers to a program that corresponds to the server and provides local services to the user. 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 unified service entry, and the service gateway may include a Zuul gateway, where Zuul is a gateway component in a Spring Cloud micro-service framework, i.e., a micro-service API gateway. The tenant identification is used for identifying unique tenant information. The business system can create corresponding tenant information according to different enterprise types, business data among tenants are completely isolated, and the business data can comprise business service data, work order data, organization data and the like. Aiming at the same tenant, the business system divides a user management center and an application management center corresponding to the tenant, and the user management center uses a set of unified organization, role information and user information, namely unified data of organization, role, user and the like, which can be shared by all departments in the same tenant. Different departments of the tenant can create the business service of the department on an application management center interface by logging in the management account. Each tenant, i.e., different enterprise or department, can create business application services belonging to users of different roles and different scenes under the framework of its own organization. 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 user terminal through the service gateway, the server can obtain a currently available service list from the service registration center according to the tenant identification 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. For example, Eureka (service discovery framework) Eureka is a service discovery framework developed by Netflix, is a REST-based service, and is mainly used for positioning middle-tier services running in an AWS domain to achieve the purposes of load balancing and middle-tier service failover. The Spring Cloud integrates the Spring Cloud into the sub-project Spring-Cloud-netflix thereof to realize the service discovery function of the Spring Cloud and provide the service registration service. The service configuration center is used for uniformly managing all services in the service system. Developers can dynamically update the configuration mechanism by modifying the configuration information in the service configuration center interface.
And 204, determining the downstream service instance information corresponding to the tenant identification according to the tenant identification.
After the server receives the service request sent by the terminal through the gateway, the server can search the downstream service instance information corresponding to the tenant identification from the service configuration center according to the tenant identification carried in the service request. The service instance information refers to service instance information of different versions corresponding to the same service which is released in a gray scale mode in a service system, and the service version information can comprise a formal version and a gray scale version. In a distributed system, different service instances may be deployed in different server clusters, for example, when one Web service system gradually increases from 10 ten thousand to 1000 ten thousand of daily access volume, a service request sent by a terminal may be forwarded to a corresponding downstream server address by deploying software having a load balancing function or module and the like, according to a tenant identifier carried in the service request. 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 client load balancing, for example, Ribbon, which is a component in a spring bound framework that implements client load balancing. Load balancing can be divided into hardware load balancing and software load balancing. The hardware load balancing is mainly realized by devices specially used for load balancing among client single nodes, and the software load balancing is realized by installing some software used for load balancing functions or modules and the like on a client to finish the request distribution work, for example, a Web server, an FTP server, an enterprise key application server, other key task servers and the like, the number of running copies of a new version and an old version can be quickly adjusted through the client load balancing, and meanwhile, the flow can be led into the new version according to percentage. In the present application, the traffic of an individual user can be specified to the new version by configuring a request Header (Header) in the HTTP request. For example, the client may invoke the service in an http request manner, and after receiving the service request sent by the client, the web server obtains one server address corresponding to an available downstream service instance from the maintained available server list according to a preset configuration rule or algorithm (such as linear polling, load by weight, load by traffic, and the like), and forwards the service request sent by the client to the server address.
In step 206, if the downstream service instance information carries the label service instance information of the tenant identifier, the service request is sent to the label service instance in the label service instance information.
After the server searches the downstream service instance information corresponding to the tenant identification from the service configuration center according to the tenant identification carried in the service request, if the server finds the tag service instance information of the downstream service instance information carrying the tenant identification, the server sends the service request to the tag service instance in the tag service instance information. In the gray scale service release system, the tag service instance mainly refers to a released gray scale service instance of a new version, and developers can establish a gray scale service instance cluster in a configuration interface in advance and bind specific tenant identification information to gray scale services in the gray scale service cluster, so that service requests of specific tenants are routed to the specified gray scale service instance.
And step 208, processing the service request by using the label service instance, obtaining a result corresponding to the service request and returning the result to the terminal.
If the server finds the tag service instance information of the tenant identification carried by the downstream service instance information, after the server sends the service request to the tag service instance in the tag service instance information, the server can process the service request by using the tag service instance to obtain a result corresponding to the service request and return the result to the terminal. When the tag service instance processes the service request sent by the terminal, 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. After the service sends the service request to the corresponding tag service instance, the tag service instance, i.e. the "Order" service, processes the service request sent by the terminal, and the "Order" service also needs to call 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, the 'Order' service processes the service request of the terminal by calling other services, finishing the service request of receiving collection and ordering, and returning a processing result corresponding to the service request to the corresponding terminal.
In a traditional gray release service mode, when a spring closed micro-service framework is used, a service request is subjected to client load balancing and needs to be completed by a Ribbon component, the component only has built-in strategies such as random and polling, when gray service examples of different versions are deployed under the same service and a traditional spring closed self-contained routing mode is adopted to process the service request, the service request sent by a client is evenly distributed to each service example and cannot distinguish tenants, when the system relates to gray release of services under a multi-tenant scene, no matter whether the upstream and downstream services are gray, the whole calling service link is required to be reset to release a new example, routing of a request of a specific tenant to a specified service example cannot be realized, and dynamic adjustment and control of a routing strategy according to different scenes cannot be realized.
In this embodiment, when a gray-scale service release in a multi-tenant scenario is involved and different tenants need to be isolated and different versions of service instances are released, a server receives a service request sent by a terminal through a gateway, where the service request includes a tenant identifier. And the server determines the downstream service instance information corresponding to the tenant identification according to the tenant identification. And if the server finds the tag service instance information of the tenant identification carried by the downstream service instance information, the server sends the service request to the tag service instance in the tag service instance information, processes the service request by using the tag service instance, obtains a result corresponding to the service request and returns the result to the terminal. Therefore, when different tenants need to be isolated and service instances of different versions are issued, the calling link for dynamically adjusting the service gray level issuance based on different service scenes can be realized only by changing the routing configuration information in the configuration center of the server and binding different tenants to different service clusters, so that the service request of a specific tenant is routed to the specified service instance, a series of complicated operations such as restarting and loading service configuration are avoided, the stability of the service system during updating iteration can be ensured, and the efficiency of the multi-tenant service gray level issuance is effectively improved.
In an embodiment, as shown in fig. 3, before receiving a service request sent by a terminal through a gateway, the method further includes a step of establishing a grayscale service instance cluster, which specifically includes:
And step 304, receiving a resource acquisition request sent by the terminal in a polling mode.
And step 306, returning the updated configuration information to the terminal according to the resource acquisition request, wherein the updated configuration information is used for indicating the terminal to update the metadata in the memory, and calling the gray level service instance in the updated configuration information.
Before the server receives a service request sent by the terminal through the gateway, if a developer needs to update a specific service corresponding to a certain tenant in the service system, when the grayscale service is released, the developer can update different versions of information corresponding to the specific service in a service configuration center interface deployed on the server. Specifically, a developer may establish a grayscale service instance cluster in a service configuration interface deployed on a server, and bind or delete a specific tenant identifier in the grayscale service instance cluster to obtain updated configuration information. Meanwhile, the server can receive a resource acquisition request sent by the terminal in a polling mode, and the terminal can send an http request regularly by adopting a short polling mode. The terminal can also send a request to the server by adopting a long polling mode, namely the terminal sends the request until receiving a message returned by the server or the terminal continues to send the next request after the request is overtime. For example, for a certain instant messaging application program, a developer updates the grayscale version a1.2 corresponding to the service a in the service configuration center interface, updates the tenant identifier bound to the grayscale version a1.2 of the service a in the grayscale service instance cluster corresponding to the service a, deletes the grayscale version a1.1 of the service a originally bound to the tenant identifier, and obtains updated configuration information. When the server receives a resource acquisition request sent by the terminal in a polling manner, the server can return the updated configuration information to the corresponding terminal according to the resource acquisition request sent by the terminal, so that the terminal updates the metadata in the memory, and calls the updated gray-scale service instance a1.2 bound with the tenant identifier according to the updated configuration information, that is, the terminal calls the routing information corresponding to the service according to the tenant identifier, and the routing information corresponding to the service is changed from the original a1.1 version of the service a to the a1.2 version of the service a, that is, the updated a1.2 version of the service a is called. Therefore, the tenant is bound by establishing the service cluster in the configuration interface, the requirements of different service scenes are better met, and the tenant can be quickly mastered by non-professionals, so that the tenant is more convenient and flexible. Meanwhile, the tenant and the service instance are used as the minimum unit to perform designated service request routing control, different service instances are divided into different clusters, different tenants are bound to different service clusters, the request of the designated tenant is routed to the designated service instance, and the routing link is dynamically adjusted according to different service scenes by combining a front-end interface.
In an embodiment, after receiving the service request sent by the terminal through the gateway, the method further includes a step of searching for the downstream service instance information that does not exist and corresponds to the tenant identifier, and specifically includes:
and according to the tenant identification, if the downstream service instance information corresponding to the tenant identification does not exist in the searching process, the service request is sent to the corresponding non-gray level service instance according to the original routing strategy.
After the server receives the service request sent by the terminal through the gateway, the server can search the downstream service instance information corresponding to the tenant identification from the service configuration center according to the tenant identification carried in the service request. And the server performs traversal search from the service configuration center, and if the server searches that the downstream service instance information corresponding to the tenant identification does not exist, the server sends the service request to the corresponding non-gray level service instance according to the original routing strategy. In a service system, the function of a certain application is updated, after a corresponding 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 operating state of the new version, collect data in various operation processes, compare various data of the new version and the old version, and 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 gray-scale service is released, after the developer confirms that the new version of the gray-scale release operates well, the developer can gradually introduce more traffic into the new version, and the developer can modify part of tenants in a service configuration center interface to call the service of the new version, that is, the developer binds or deletes a specific tenant identifier in a gray-scale service instance cluster corresponding to the service, so that the part of the bound tenants call the service of the new version, and the rest of the tenants do not bind any gray-scale service instance cluster, and then the other tenants call the service instance of the normal version corresponding to the service, that is, the non-gray-scale service instance, according to the original routing policy. Therefore, if a new version is found to have problems in the gray release process (gray period), the routing rule is issued by updating the cache of the metadata, and the performance is higher. Meanwhile, codes are directly expanded at a server side, so that the problem of performance loss caused by simultaneous calling of a plurality of services can be solved. Each service requests to acquire real-time updated configuration information in a polling mode, a routing link can be dynamically adjusted without taking the link service of the whole service off-line, the negative influence of the gray level release can be controlled in a minimum range, the stability of a service system during update iteration is ensured, and meanwhile, the efficiency of multi-tenant service gray level release is effectively improved.
In one embodiment, as shown in fig. 4, a multi-tenant service gray scale publishing method 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 404, determining downstream service instance information corresponding to the tenant identification according to the tenant identification.
In step 406, if the downstream service instance information carries the tag service instance information of the tenant identifier, a list of all tag service instances carrying the tenant identifier is obtained.
And step 408, calling the corresponding label service instance from the label service instance information list according to a preset weight proportion, and sending the service request to the label service instance.
And step 410, if the downstream service instance information does not carry the label service instance information of the tenant identification, sending the service request to the corresponding non-grayscale downstream service instance according to the original routing strategy.
When a developer needs to update a service corresponding to SH01 identified by a tenant in a service system and issues a corresponding grayscale service, the developer can update different versions of information corresponding to the service in a service configuration center interface deployed on a server. For example, the service registration center Eureka provides a rest interface to modify the metadata, and the method is invoked locally in the server to directly modify the metadata to reduce the loss, and meanwhile, the modified configuration information is stored in the database, so that the data recovery of the service instance can be realized for the hung service instance. For example, a remote Dictionary service (Redis) is an open source log-type and Key-Value database written in ANSIC language, supporting network, based on memory and persistent, and provides API of multiple languages. And storing instance metadata corresponding to all modification operations in the redis for persistence in all configuration change operations of the configuration center. Conventionally, when metadata is set through http request calling, a large amount of metadata operations are generated, each time an http request needs to be initiated for modification, and a large amount of resource loss is caused. For example, the server may monitor the service configuration center through a time mechanism of the spring Cloud framework, that is, monitor the eureka instant registered event, and when the service carrying the meta-information is found to be online again, the server resets the corresponding persistent meta-information to the online service instance. For example, after the user reconfigures the configuration data corresponding to the meta-information a4001, and when the server monitors that the service carrying the meta-information a4001 in the service configuration center comes online again, the server resets the persistent meta-information a4001 stored in the redis to the online service instance, thereby restoring the instance data of the hung-up service instance.
Specifically, a developer may directly update new versions corresponding to the service a and the service B in the service configuration center interface, that is, grayscale versions are svca1.1, svca1.2, and svcb1.1, modify configuration information corresponding to the service a, update tenant identifiers bound to the grayscale versions a1.1 and a1.2 of the service a in the grayscale service instance cluster corresponding to the service a, delete the grayscale version a1.0 of the service a originally bound to the tenant identifier SH01, and obtain updated configuration information. When the server receives a service request sent by the terminal through the gateway, the server searches the downstream service instance information corresponding to the tenant identification SH01 from the service configuration center according to the tenant identification SH01 carried in the service request. If the server finds out that the downstream service instance information carries the label service instance information of the tenant identification SH01, the server acquires all label service instance information lists carrying the tenant identification SH 01. In addition, the developer may also modify the weight proportion data of different versions corresponding to the service a, that is, the developer may preset a corresponding routing rule or weight proportion in the service configuration center interface. Such as provisioning version 1.1 and version 1.2 of service a, accounting for 90% and 10% of the total traffic, respectively. Meanwhile, different versions of traffic distribution work can be completed through software or modules with load balancing functions, such as a proxy server or a Ribbon component. The server may select a corresponding tag service instance from the tag service instance information list as the a1.2 version of the service a according to the preset weight proportion, and send the service request to the tag service instance a 1.2. The server processes the service request by using the tag service instance a1.2, obtains a result corresponding to the service request and returns the result to the terminal. If the server finds that the downstream service instance information does not carry the label service instance information of the tenant identification, the server sends the service request to the corresponding non-gray downstream service instance A1.0 according to the original routing strategy, namely the server sends the service request to the corresponding normal version service instance A1.0 according to the preset default routing configuration information. And the server processes the service request by using the non-gray downstream service instance A1.0 to obtain a result corresponding to the service request and returns the result to the terminal. Therefore, by dividing the cluster, other idle service instances can be called for service requests without specific use scenes, all the service instances can be ensured to receive flow, and the condition of resource waste of the deployed service instances is greatly reduced. Meanwhile, zero intrusion is realized by means of integration of an upgrade data packet (sdk), no code or configuration is added, metadata can be configured, updated and issued at a server side in a data packet upgrade mode, and self-defined service routing is performed through client load balancing, so that service requests of specific tenants are routed to a specified service instance, a series of tedious operations such as restarting and loading service configuration are avoided, stability of a service system during update iteration can be guaranteed, and meanwhile, the efficiency of multi-tenant service gray release is effectively improved.
In one embodiment, before the server receives the service request sent by the terminal through the gateway, the method further includes: and configuring the attribute of the service request sent by the terminal in the basic data packet, so that the gateway extracts the corresponding tenant identification from the service request sent by the terminal, adds the tenant identification to the service calling request and forwards the tenant identification to the corresponding downstream service instance. At the Ribbon client, developers can customize different downstream service calling strategies according to different scenes, namely the developers only need to write a custom strategy in a basic data packet and register a custom JavaBean to realize the method. The JavaBean refers to a public Java class and is a reusable component written in Java language. In the user-defined load balancing client, the tenant identification carried in the service request is obtained by calling a RequestContextHolder method, that is, the service gateway can extract corresponding tenant identification information from a token (token, computer term) carried in the service request, and since a request header (header) in an http request received by the service gateway does not carry the tenant identification, it is necessary to configure an attribute of the service request sent by the terminal in advance in a basic data packet, that is, it is necessary to configure an attribute of a java bean, which is a requestInterreceptor, so that after the service request sent by the terminal is received by the service gateway, the service gateway can extract corresponding tenant identification information from the token carried by the service request and add the extracted tenant identification information to a request header of a pass-through request, for example, when the service gateway needs to forward the service request a to a corresponding gray-scale service instance a1.2, the gateway adds the extracted tenant identification to the request header (header) of the http request by calling the method of RequestContext # addZuulRequestHeader, and transparently transmits the extracted tenant identification to the corresponding service instance a 1.2. Therefore, related data is configured in the basic data packet in advance, components and client processing logic which need to be used are packaged in the basic data packet, data of the client are prevented from being reconfigured in each process, and the tenant identification information can be added to the request header of the request for transmitting the service instance through the gateway only by upgrading the version of the basic data packet of the server, so that the tenant identification information in the request header (header) in the whole request link can be kept all the time, the service request of a specific tenant is routed to the specified service instance, a series of tedious operations such as loading service configuration and the like are avoided, the stability of the service system during updating iteration can be guaranteed, and meanwhile, the gray level issuing efficiency of multi-tenant service is effectively improved.
In one embodiment, the step of processing the service request by using the tag service instance includes:
in the asynchronous thread, when the tag service instance needs to call other service instances to process a service request, a tenant identification is preferentially obtained from the gateway thread, and when the tenant identification is used for calling between service instances, the version of the service instance matched with the tenant identification is selected from the service instances of different versions corresponding to the same service. The asynchronous thread means that when the thread pool is used for isolation, a newly started asynchronous thread cannot acquire information of a current thread, namely when calling between services, cross-process calling is performed, the calling between services is equivalent to re-initiating a service request, and a request header is not set in the newly initiated request, so that information in an original service request header which cannot be carried, namely tenant id information in an original request header (header) is lost, and therefore, tenant identification information is acquired from a gateway thread preferentially to avoid the problem of tenant information loss. For example, when the server receives a service request sent by the terminal through the gateway, the server searches the downstream service instance information corresponding to the tenant identity SH01 from the service configuration center according to the tenant identity SH01 carried in the service request. If the server finds that the downstream service instance information carries the label service instance information of the tenant identity SH01, the server may select a corresponding label service instance from the label service instance information list as the a1.2 version of the service a according to a preset weight proportion, and send the service request to the label service instance a 1.2. When the server processes the service request by using the tag service instance a1.2, when the tag service instance a1.2 needs to call the service B to process the service request, the server can preferentially obtain a tenant identity from a service gateway thread, that is, the server can obtain information corresponding to a current thread from a thread variable of log4j, after the server obtains the tenant identity from the gateway thread, the server calls a service instance version matching the tenant identity from a gray scale service instance cluster corresponding to the service B according to the tenant identity, for example, B1.2 in the gray scale service instance cluster corresponding to the service B has a binding relationship with the tenant identity SH01, when the server processes the service request by using the tag service instance a1.2, so that the tag service instance a1.2 calls the service instance B1.2 matching the tenant identity from the gray scale service instance cluster corresponding to the service B according to the tenant identity to cooperatively process the service request sent by the terminal, after the service a1.2 and the service B1.2 have finished processing the service request, a result corresponding to the service request is obtained, and the server returns the service processing result to the corresponding terminal. Therefore, even in an asynchronous thread, the calling link for dynamically adjusting the service gray release based on different service scenes can be realized by acquiring the tenant identification information carried in the original service request in the log information from the gateway thread, so that the service request of a specific tenant is routed to the specified service instance.
It should be understood that although the various steps in the flow charts of fig. 1-4 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-4 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. 5, there is provided a multi-tenant service gray scale issuing apparatus including: a receiving module 502, a determining module 504, a sending module 506, and a processing module 508, wherein:
a receiving module 502, configured to receive a service request sent by a terminal through a gateway, where the service request includes a tenant identity.
A determining module 504, configured to determine, according to the tenant identifier, downstream service instance information corresponding to the tenant identifier.
A sending module 506, configured to send the service request to the tag service instance in the tag service instance information if the downstream service instance information carries the tag service instance information of the tenant identifier.
And the processing module 508 is configured to process the service request by using the tag service instance, obtain a result corresponding to the service request, and return the result to the terminal.
In one embodiment, the apparatus further comprises: an update module and a return module.
The updating module is used for establishing a gray-scale service instance cluster in the configuration interface, and binding or deleting a specific tenant identification in the gray-scale service instance cluster to obtain updated configuration information. The receiving module is further used for receiving the resource obtaining request sent by the terminal in a polling mode. And the returning module is used for returning the updated configuration information to the terminal according to the resource acquisition request, wherein the updated configuration information is used for indicating the terminal to update the metadata in the memory and calling the gray level service instance in the updated configuration information.
In an embodiment, the sending module is further configured to send the service request to the corresponding non-grayscale service instance according to the original routing policy if there is no downstream service instance information corresponding to the tenant identity.
In one embodiment, the apparatus further comprises: the device comprises an acquisition module and a calling module.
The acquisition module is used for acquiring all tag service instance information lists carrying tenant identification. And the calling module is used for calling the corresponding label service instance from the label service instance information list according to a preset weight proportion.
In one embodiment, the sending module is further configured to send the service request to the corresponding non-grayscale downstream service instance according to an original routing policy if the downstream service instance information does not carry the tag service instance information of the tenant identifier.
In one embodiment, the apparatus further comprises: and configuring the module.
The configuration module is used for configuring the attribute of the service request sent by the terminal in the basic data packet, so that the gateway extracts the corresponding tenant identification from the service request sent by the terminal, adds the tenant identification to the service request and forwards the tenant identification to the corresponding downstream service instance.
In one embodiment, the obtaining module is further configured to, in the asynchronous thread, preferentially obtain the tenant identifier from the gateway thread when the tag service instance needs to call another service instance to process the service request, where the tenant identifier is used to call a service instance version matching the tenant identifier from service instances of different versions corresponding to the same service when the tenant identifier is called between the service instances.
For specific limitations of the multi-tenant service grayscale issuing device, reference may be made to the above limitations of the multi-tenant service grayscale issuing method, and details are not described here. The modules in the multi-tenant service gray level issuing device 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. 6. 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 configuration data of multi-tenant service gray scale release. 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 multi-tenant service gray scale publishing method.
Those skilled in the art will appreciate that the architecture shown in fig. 6 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 multi-tenant service gray scale publishing method, the method comprising:
receiving a service request sent by a terminal through a gateway, wherein the service request comprises a tenant identification;
determining downstream service instance information corresponding to the tenant identification according to the tenant identification;
if the downstream service instance information carries the label service instance information of the tenant identification, the service request is sent to the label service instance in the label service instance information;
and processing the service request by using the label service instance to obtain a result corresponding to the service request and returning the result to the terminal.
2. The method of claim 1, wherein before the receiving the service request sent by the terminal through the gateway, the method further comprises:
establishing a gray-scale service instance cluster in a configuration interface, and binding or deleting a specific tenant identification in the gray-scale service instance cluster to obtain updated configuration information;
receiving a resource acquisition request sent by the terminal in a polling mode;
and returning the updated configuration information to the terminal according to the resource acquisition request, wherein the updated configuration information is used for indicating the terminal to update the metadata in the memory and calling the gray level service instance in the updated configuration information.
3. The method of claim 1, wherein after receiving the service request sent by the terminal through the gateway, the method further comprises:
and according to the tenant identification, if the downstream service instance information corresponding to the tenant identification does not exist in the searching process, the service request is sent to the corresponding non-gray level service instance according to the original routing strategy.
4. The method according to claim 1, wherein after the step of sending the service request to the tag service instance in the tag service instance information if the downstream service instance information carries the tag service instance information of the tenant identity, the method further comprises:
acquiring all tag service instance information lists carrying the tenant identification;
and calling the corresponding label service instance from the label service instance information list according to a preset weight proportion.
5. The method of claim 1, further comprising:
and if the downstream service instance information does not carry the label service instance information of the tenant identification, sending the service request to a corresponding non-grayscale downstream service instance according to an original routing strategy.
6. The method of claim 1, wherein before the receiving the service request sent by the terminal through the gateway, the method further comprises:
and configuring the attribute of the service request sent by the terminal in the basic data packet, so that the gateway extracts the corresponding tenant identification from the service request sent by the terminal, adds the tenant identification to the service request and forwards the tenant identification to the corresponding downstream service instance.
7. The method of claim 1, wherein the processing the service request with the tag service instance comprises:
in an asynchronous thread, when the tag service instance needs to call other service instances to process the service request, a tenant identification is preferentially obtained from a gateway thread; and the tenant identification is used for calling the service instance version matched with the tenant identification from the service instances of different versions corresponding to the same service when calling between the service instances.
8. A multi-tenant service gray scale distribution apparatus, the apparatus comprising:
the system comprises a receiving module, a sending module and a processing module, wherein the receiving module is used for receiving a service request sent by a terminal through a gateway, and the service request comprises a tenant identification;
the determining module is used for determining downstream service instance information corresponding to the tenant identification according to the tenant identification;
a sending module, configured to send the service request to a tag service instance in the tag service instance information if the downstream service instance information carries the tag service instance information of the tenant identifier;
and the processing module is used for processing the service request by using the label service instance, obtaining a result corresponding to the service request and returning the result to the terminal.
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 |
|---|---|---|---|
| CN202010817357.4A CN112118565B (en) | 2020-08-14 | 2020-08-14 | Multi-tenant service gray level publishing method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010817357.4A CN112118565B (en) | 2020-08-14 | 2020-08-14 | Multi-tenant service gray level publishing method, device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112118565A true CN112118565A (en) | 2020-12-22 |
| CN112118565B CN112118565B (en) | 2023-07-25 |
Family
ID=73804160
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010817357.4A Active CN112118565B (en) | 2020-08-14 | 2020-08-14 | Multi-tenant service gray level publishing method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112118565B (en) |
Cited By (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112631804A (en) * | 2020-12-25 | 2021-04-09 | 杭州涂鸦信息技术有限公司 | Service call request processing method based on isolation environment and computer equipment |
| CN112866268A (en) * | 2021-01-29 | 2021-05-28 | 中国工商银行股份有限公司 | Message processing method and system |
| CN113055492A (en) * | 2021-03-25 | 2021-06-29 | 深圳云之家网络有限公司 | Control method and device for service gray scale link, computer equipment and storage medium |
| CN113127550A (en) * | 2021-04-21 | 2021-07-16 | 北京字跳网络技术有限公司 | Information processing method, information processing device, electronic equipment and storage medium |
| CN113259407A (en) * | 2021-03-25 | 2021-08-13 | 上海卓悠网络科技有限公司 | Data interaction method and device based on application market architecture |
| CN113271334A (en) * | 2021-03-25 | 2021-08-17 | 西藏宁算科技集团有限公司 | Service strategy distribution method and device based on SaaS scene and electronic equipment |
| CN113329096A (en) * | 2021-06-23 | 2021-08-31 | 未鲲(上海)科技服务有限公司 | Message transmission method and device, electronic equipment and storage medium |
| CN113407967A (en) * | 2021-06-25 | 2021-09-17 | 上海卓悠网络科技有限公司 | Service security method and device based on application market architecture |
| CN113422732A (en) * | 2021-06-22 | 2021-09-21 | 康键信息技术（深圳）有限公司 | Version updating method, device, equipment and storage medium based on total station gray scale |
| CN113535744A (en) * | 2021-07-09 | 2021-10-22 | 深圳市蘑菇财富技术有限公司 | Tenant data modification method, system, device and storage medium |
| CN113791805A (en) * | 2021-09-17 | 2021-12-14 | 马上消费金融股份有限公司 | Micro-service gray level publishing method and device |
| CN113867992A (en) * | 2021-12-03 | 2021-12-31 | 连连（杭州）信息技术有限公司 | Call chain resource isolation method and device, storage medium and electronic equipment |
| CN114143324A (en) * | 2021-10-27 | 2022-03-04 | 上海卓悠网络科技有限公司 | Load balancing method and device based on application market architecture |
| CN114422440A (en) * | 2022-03-28 | 2022-04-29 | 北京沃丰时代数据科技有限公司 | Gray scale distribution method and device, electronic equipment and storage medium |
| CN114675896A (en) * | 2020-12-24 | 2022-06-28 | 广东飞企互联科技股份有限公司 | Parameter configuration method and system for micro-service development |
| CN114978998A (en) * | 2021-02-26 | 2022-08-30 | 中移(苏州)软件技术有限公司 | Flow control method, device, terminal and storage medium |
| CN115002227A (en) * | 2022-05-19 | 2022-09-02 | 青岛海尔科技有限公司 | User access request response method, storage medium and electronic device |
| CN115103028A (en) * | 2022-07-22 | 2022-09-23 | 深圳竹云科技股份有限公司 | SaaS application request processing method and device and computer equipment |
| CN115208869A (en) * | 2022-07-20 | 2022-10-18 | 康键信息技术（深圳）有限公司 | Processing method, device, equipment and medium for gray scale release |
| CN115269040A (en) * | 2022-07-22 | 2022-11-01 | 广州市玄武无线科技股份有限公司 | Tenant business application expanding method, device and system |
| WO2022228121A1 (en) * | 2021-04-27 | 2022-11-03 | 华为云计算技术有限公司 | Service providing method and apparatus |
| CN115361436A (en) * | 2022-08-18 | 2022-11-18 | 中国工商银行股份有限公司 | Starting method and device of personalized service instance and electronic equipment |
| CN115474071A (en) * | 2022-08-22 | 2022-12-13 | 北京达佳互联信息技术有限公司 | Content display method, device, equipment and storage medium |
| WO2023116151A1 (en) * | 2021-12-22 | 2023-06-29 | 中兴通讯股份有限公司 | Service processing method and system, and computer-readable storage medium |
| CN116860381A (en) * | 2023-09-04 | 2023-10-10 | 厦门民航凯亚有限公司 | Method for releasing visual micro-service gray scale |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109412878A (en) * | 2019-01-16 | 2019-03-01 | 紫光云数科技有限公司 | Multi-tenant service access implementation method, device and electronic equipment |
| CN109510852A (en) * | 2017-09-15 | 2019-03-22 | 阿里巴巴集团控股有限公司 | The method and device of gray scale publication |
| US20190182226A1 (en) * | 2017-12-11 | 2019-06-13 | International Business Machines Corporation | Provide access to data storage services in a network environment |
| CN111092816A (en) * | 2019-11-26 | 2020-05-01 | 金蝶软件（中国）有限公司 | Gateway dynamic routing method, gateway dynamic routing device, computer equipment and storage medium |
| CN111478961A (en) * | 2020-04-03 | 2020-07-31 | 中国建设银行股份有限公司 | Multi-tenant service calling method and device |
-
2020
- 2020-08-14 CN CN202010817357.4A patent/CN112118565B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109510852A (en) * | 2017-09-15 | 2019-03-22 | 阿里巴巴集团控股有限公司 | The method and device of gray scale publication |
| US20190182226A1 (en) * | 2017-12-11 | 2019-06-13 | International Business Machines Corporation | Provide access to data storage services in a network environment |
| CN109412878A (en) * | 2019-01-16 | 2019-03-01 | 紫光云数科技有限公司 | Multi-tenant service access implementation method, device and electronic equipment |
| CN111092816A (en) * | 2019-11-26 | 2020-05-01 | 金蝶软件（中国）有限公司 | Gateway dynamic routing method, gateway dynamic routing device, computer equipment and storage medium |
| CN111478961A (en) * | 2020-04-03 | 2020-07-31 | 中国建设银行股份有限公司 | Multi-tenant service calling method and device |
Cited By (37)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114675896A (en) * | 2020-12-24 | 2022-06-28 | 广东飞企互联科技股份有限公司 | Parameter configuration method and system for micro-service development |
| CN112631804A (en) * | 2020-12-25 | 2021-04-09 | 杭州涂鸦信息技术有限公司 | Service call request processing method based on isolation environment and computer equipment |
| CN112631804B (en) * | 2020-12-25 | 2024-05-24 | 杭州涂鸦信息技术有限公司 | Service call request processing method based on isolation environment and computer equipment |
| CN112866268A (en) * | 2021-01-29 | 2021-05-28 | 中国工商银行股份有限公司 | Message processing method and system |
| CN114978998A (en) * | 2021-02-26 | 2022-08-30 | 中移(苏州)软件技术有限公司 | Flow control method, device, terminal and storage medium |
| CN114978998B (en) * | 2021-02-26 | 2023-12-12 | 中移(苏州)软件技术有限公司 | Flow control method, device, terminal and storage medium |
| CN113055492A (en) * | 2021-03-25 | 2021-06-29 | 深圳云之家网络有限公司 | Control method and device for service gray scale link, computer equipment and storage medium |
| CN113259407A (en) * | 2021-03-25 | 2021-08-13 | 上海卓悠网络科技有限公司 | Data interaction method and device based on application market architecture |
| CN113271334A (en) * | 2021-03-25 | 2021-08-17 | 西藏宁算科技集团有限公司 | Service strategy distribution method and device based on SaaS scene and electronic equipment |
| CN113271334B (en) * | 2021-03-25 | 2023-07-21 | 西藏宁算科技集团有限公司 | Service policy distribution method and device based on SaaS scene and electronic equipment |
| CN113259407B (en) * | 2021-03-25 | 2023-02-03 | 上海卓悠网络科技有限公司 | Data interaction method and device based on application market architecture |
| CN113127550A (en) * | 2021-04-21 | 2021-07-16 | 北京字跳网络技术有限公司 | Information processing method, information processing device, electronic equipment and storage medium |
| WO2022228121A1 (en) * | 2021-04-27 | 2022-11-03 | 华为云计算技术有限公司 | Service providing method and apparatus |
| 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 |
| CN113329096A (en) * | 2021-06-23 | 2021-08-31 | 未鲲(上海)科技服务有限公司 | Message transmission method and device, electronic equipment and storage medium |
| CN113407967A (en) * | 2021-06-25 | 2021-09-17 | 上海卓悠网络科技有限公司 | Service security method and device based on application market architecture |
| CN113407967B (en) * | 2021-06-25 | 2023-02-07 | 上海卓悠网络科技有限公司 | Service security method and device based on application market architecture |
| CN113535744A (en) * | 2021-07-09 | 2021-10-22 | 深圳市蘑菇财富技术有限公司 | Tenant data modification method, system, device and storage medium |
| CN113535744B (en) * | 2021-07-09 | 2023-12-08 | 深圳市蘑菇财富技术有限公司 | Tenant data modification method, system, equipment and storage medium |
| CN113791805A (en) * | 2021-09-17 | 2021-12-14 | 马上消费金融股份有限公司 | Micro-service gray level publishing method and device |
| CN114143324A (en) * | 2021-10-27 | 2022-03-04 | 上海卓悠网络科技有限公司 | Load balancing method and device based on application market architecture |
| CN113867992B (en) * | 2021-12-03 | 2022-03-25 | 连连（杭州）信息技术有限公司 | Call chain resource isolation method and device, storage medium and electronic equipment |
| CN113867992A (en) * | 2021-12-03 | 2021-12-31 | 连连（杭州）信息技术有限公司 | Call chain resource isolation method and device, storage medium and electronic equipment |
| WO2023116151A1 (en) * | 2021-12-22 | 2023-06-29 | 中兴通讯股份有限公司 | Service processing method and system, and computer-readable storage medium |
| CN114422440A (en) * | 2022-03-28 | 2022-04-29 | 北京沃丰时代数据科技有限公司 | Gray scale distribution method and device, electronic equipment and storage medium |
| CN115002227A (en) * | 2022-05-19 | 2022-09-02 | 青岛海尔科技有限公司 | User access request response method, storage medium and electronic device |
| CN115002227B (en) * | 2022-05-19 | 2024-03-22 | 青岛海尔科技有限公司 | User access request response method, storage medium and electronic device |
| CN115208869A (en) * | 2022-07-20 | 2022-10-18 | 康键信息技术（深圳）有限公司 | Processing method, device, equipment and medium for gray scale release |
| CN115103028A (en) * | 2022-07-22 | 2022-09-23 | 深圳竹云科技股份有限公司 | SaaS application request processing method and device and computer equipment |
| CN115269040B (en) * | 2022-07-22 | 2023-04-14 | 广州市玄武无线科技股份有限公司 | Tenant business application expanding method, device and system |
| CN115269040A (en) * | 2022-07-22 | 2022-11-01 | 广州市玄武无线科技股份有限公司 | Tenant business application expanding method, device and system |
| CN115361436A (en) * | 2022-08-18 | 2022-11-18 | 中国工商银行股份有限公司 | Starting method and device of personalized service instance and electronic equipment |
| CN115474071A (en) * | 2022-08-22 | 2022-12-13 | 北京达佳互联信息技术有限公司 | Content display method, device, equipment and storage medium |
| CN115474071B (en) * | 2022-08-22 | 2024-05-14 | 北京达佳互联信息技术有限公司 | Content display method, device, 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112118565B (en) | 2023-07-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112118565A (en) | Multi-tenant service gray level publishing method and device, computer equipment and storage medium | |
| CN112000348A (en) | Control method and device for service gray release and computer equipment | |
| US10776171B2 (en) | Endpoint management system and virtual compute system | |
| US11714675B2 (en) | Virtualization-based transaction handling in an on-demand network code execution system | |
| US10884787B1 (en) | Execution guarantees in an on-demand network code execution system | |
| US20200341741A1 (en) | Cross-environment application of tracing information for improved code execution | |
| US10528390B2 (en) | Idempotent task execution in on-demand network code execution systems | |
| US11836516B2 (en) | Reducing execution times in an on-demand network code execution system using saved machine states | |
| CN111314141B (en) | Route updating method and device | |
| CN112035228B (en) | Resource scheduling method and device | |
| US10977226B2 (en) | Self-service configuration for data environment | |
| US11347555B2 (en) | Integrated system to distribute and execute complex applications | |
| US11842222B2 (en) | Using scripts to bootstrap applications with metadata from a template | |
| US10257110B2 (en) | Using a template to update a stack of resources | |
| US11010215B2 (en) | Recommending applications based on call requests between applications | |
| US20120096043A1 (en) | Data graph cloud system and method | |
| CN113055492A (en) | Control method and device for service gray scale link, computer equipment and storage medium | |
| US8893272B2 (en) | Method and device for recombining runtime instruction | |
| US9378039B2 (en) | Virtual machine storage replication schemes | |
| US20140282630A1 (en) | Backend custom code extensibility | |
| CN111090423A (en) | Webhook framework system and method for realizing active calling and event triggering | |
| CN114168179B (en) | Micro-service management method, micro-service management device, computer equipment and storage medium | |
| CN112463808A (en) | Data processing method and device of target cluster and server | |
| US10599453B1 (en) | Dynamic content generation with on-demand code execution | |
| CN112988584A (en) | Service testing method, 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address |
Address after: Room 501, No. 55 Tiyu West Road, Tianhe District, Guangzhou City, Guangdong Province, 510665, self-made B103 Patentee after: Kingdee Medical Software Technology Co.,Ltd. Country or region after: China Address before: Room 01-10, 20 / F, 21 Xingguo Road, Tianhe District, Guangzhou City, Guangdong Province Patentee before: KINGDEE MEDICAL SOFTWARE TECHNOLOGY Co.,Ltd. Country or region before: China |