CN115756806A - Product service iteration method and device, electronic equipment and storage medium - Google Patents
Product service iteration method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115756806A CN115756806A CN202211542152.5A CN202211542152A CN115756806A CN 115756806 A CN115756806 A CN 115756806A CN 202211542152 A CN202211542152 A CN 202211542152A CN 115756806 A CN115756806 A CN 115756806A
- Authority
- CN
- China
- Prior art keywords
- service
- cluster
- product
- product service
- address
- 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
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the invention discloses a product service iteration method, a product service iteration device, electronic equipment and a storage medium. The method comprises the following steps: responding to a product service calling request, and determining product services to be called, wherein the product services can be respectively deployed on at least two server clusters; determining an extraction cluster from each server cluster according to the tangential flow configuration of the product service, wherein the extraction cluster is used for providing the product service; and forwarding the product service calling request to the product service deployed on the service-providing cluster so as to realize the calling process of the product service and the iterative process on the service-stopping cluster, wherein the service-stopping cluster comprises clusters except the service-providing cluster in at least two server clusters, and the service-stopping cluster stops providing the product service. According to the technical scheme of the embodiment of the invention, the iterative process of the product service can be realized through the tangential flow operation of the product service dimension, so that the realization efficiency and the success rate of the iterative process are ensured.
Description
Technical Field
The embodiment of the invention relates to the technical field of computer application, in particular to a product service iteration method and device, electronic equipment and a storage medium.
Background
With the rapid development of cloud computing technology, software-as-a-Service (SAAS) platforms are gradually emerging. The SAAS platform is a platform for providing product services through a network, and is very attractive to small and medium-sized enterprises with limited cost budgets and insufficient technical conditions.
To ensure high availability of the product service, the product service on the SAAS platform is deployed on at least two clusters of servers. On this basis, in order to ensure that the product service provides uniform use experience for users, an iterative process needs to be respectively implemented for the product service on each server cluster. Currently, the above iterative process is mainly implemented by a tangential flow operation of platform dimensions.
In the process of implementing the invention, the inventor finds that the following technical problems exist in the prior art: it is difficult to ensure the efficiency and success rate of the iterative process of product service.
Disclosure of Invention
The embodiment of the invention provides a product service iteration method, a product service iteration device, electronic equipment and a storage medium, and solves the problem that the realization efficiency and the success rate of an iteration process of product service are difficult to guarantee.
According to an aspect of the present invention, there is provided a product service iteration method, which may include:
responding to a product service calling request, and determining product services to be called, wherein the product services can be respectively deployed on at least two server clusters;
determining an extraction cluster from each server cluster according to the tangential flow configuration of the product service, wherein the extraction cluster is used for providing the product service;
and forwarding the product service calling request to a product service deployed on the service-providing cluster to realize the calling process of the product service and the iteration process on the service-stopping cluster, wherein the service-stopping cluster is a cluster except the service-providing cluster in at least two server clusters, and the service-stopping cluster stops providing the product service.
According to another aspect of the present invention, there is provided a product service iteration apparatus, which may include:
the product service determining module is used for responding to the product service calling request and determining the product service to be called, wherein the product service is respectively deployed on at least two server clusters;
the system comprises a service-providing cluster determining module, a service-providing cluster determining module and a service-providing cluster determining module, wherein the service-providing cluster determining module is used for determining a service-providing cluster from each server cluster according to the tangential flow configuration of the product service;
and the product service iteration module is used for forwarding the product service calling request to the product service deployed on the service-providing cluster so as to realize the calling process of the product service and the iteration process on the service-stopping cluster, wherein the service-stopping cluster is a cluster except the service-providing cluster in at least two server clusters, and the service-stopping cluster stops providing the product service.
According to another aspect of the present invention, there is provided an electronic device, which may include:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to cause the at least one processor, when executed, to implement a product-service iteration method provided by any embodiment of the invention.
According to another aspect of the present invention, there is provided a computer readable storage medium having stored thereon computer instructions for causing a processor to execute a method of product service iteration provided by any of the embodiments of the present invention.
According to the technical scheme of the embodiment of the invention, the product service to be called is determined by responding to the product service calling request, and in order to ensure the high availability of the product service, the product service is respectively deployed on at least two server clusters; determining a service providing cluster for providing the product service (namely, the online flow responsible for the product service) from each server cluster according to the flow switching configuration of the product service; the product service calling request is forwarded to the product service deployed on the service-providing cluster, so that the calling process of the product service is realized, and the service-stopping cluster except the service-providing cluster in at least two server clusters is no longer responsible for the online flow of the product service, so that the iterative process of the product service on the service-stopping cluster can be realized under the condition that a user does not perceive. According to the technical scheme, the iterative process of the product service is realized through the tangential flow operation of the product service dimension, so that the realization efficiency and the success rate of the iterative process of the product service are ensured.
It should be understood that the statements in this section do not necessarily identify key or critical features of any embodiment of the present invention, nor do they necessarily limit the scope of the present invention. Other features of the present invention will become apparent from the following description.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a flow chart of a product service iteration method provided according to an embodiment of the invention;
FIG. 2 is a flow chart of yet another product service iteration method provided in accordance with an embodiment of the present invention;
FIG. 3 is a flow chart of another iterative method of product services provided in accordance with an embodiment of the present invention;
FIG. 4 is an architectural diagram of an alternative example of another product service iteration method provided in accordance with an embodiment of the present invention;
fig. 5 is a block diagram of a product service iteration apparatus according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of an electronic device implementing a product service iteration method according to an embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, shall fall within the protection scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. The cases of "target", "original", etc. are similar and will not be described in detail herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In order to better understand how the product service iteration method described in the embodiment of the present invention ensures the implementation efficiency of the iteration process of the product service, the following description will first perform an exemplary description on the iteration process implemented by the tangential flow operation of the platform dimension described in the background art. Illustratively, taking the SAAS platform as an example, in order to ensure that each service product on the SAAS platform provides a uniform use experience for the user, a uniform gateway architecture design is adopted here to standardize the platform technical architecture and design style. Specifically, assume that a product service a, a product service B, a product service C, and a gateway service are accessed on the SAAS platform, and a main cluster (i.e., a main server cluster) and a standby cluster (i.e., a standby server cluster) are provided to ensure high availability, then the four services are deployed under both clusters. The SAAS platform provides a unified platform domain name (hereinafter abbreviated as domain name) (e.g., www.xxx.com) as an entry to the user, so that the user accesses the domain name through a browser to invoke a product service on the SAAS platform. For example, the domain name service on the SAAS platform resolves the domain name to a gateway service of a certain cluster, and then forwards a product service invocation request sent by a user through a browser to a corresponding product service under the cluster through the gateway service, thereby implementing the invocation process of the product service.
It should be noted that, since the domain name is resolved to which cluster, which is controllable, the service product can be smoothly brought on line by performing resolution switching of different clusters on the domain name. For example, taking a product service a as an example, what is currently online (i.e., deployed on a primary/standby cluster) is a product service a of version 1.0, and an online product service a of version 2.0 is now needed, which may be implemented by the following steps:
1. resolving a domain name into a main cluster gateway example, and issuing and verifying product A service under a standby cluster if the standby cluster does not have any production flow;
2. after the product service A under the standby cluster is issued and verified, resolving the domain name to a gateway example of the standby cluster, and if the main cluster does not have any production flow, issuing and verifying the product service A under the main cluster;
3. after the product A service in the main cluster is released and verified, the domain name is simultaneously resolved to the gateway examples of the main cluster and the standby cluster so as to simultaneously support the online flow of the product A service.
As can be seen from the above, this is a cut-flow operation of product dimensions (i.e., a cut-flow is realized by resolving a domain name to different cluster gateway instances), i.e., in an iterative process of realizing a product service under a primary cluster, a backup cluster does not have any production traffic, and vice versa, so that the iterative process of the product service can be realized without perception by a user, i.e., in a process of allowing a user to normally apply a certain product service, the iterative process of the product service is realized.
It should be noted that, the implementation scheme of the iterative process of completing the product service through the tangential flow operation of the product dimension is still feasible when the number of product services accessed on the SAAS platform is limited and the iteration frequency of each product service is low. However, when the SAAS platform has more product services and/or the iteration frequency of each product service is higher, the above implementation scheme easily leads to a high online rhythm of the SAAS platform, and thus has the following problems:
on one hand, the number of product services needing iteration in the same time period is large, and because all the product services need to be subjected to flow switching through domain name resolution, the flow switching of the main and standby clusters can be performed only after each product service needing online deployment is verified to be passed, so when a problem occurs in the issuing verification process of a certain product service or a certain number of product services and the problem cannot be solved later, other product services needing online deployment are caused to wait all the time, the online deployment time is caused to be continuously increased, the efficiency is lower and lower, and the realization efficiency of the iteration process is difficult to ensure.
On the other hand, the online deployment of each product service depends on domain name resolution flow switching, and whether verification is correct in the cluster currently deployed online is confirmed by each product service before the resolution flow switching.
In order to solve the above two problems, the inventor has proposed a product service iteration method set forth in each embodiment below based on a thorough study of the prior art.
Fig. 1 is a flowchart of a product service iteration method provided in an embodiment of the present invention. The embodiment can be suitable for the product service iteration condition, and is particularly suitable for the product service iteration condition realized through the tangential flow operation of the product service dimension. The method may be executed by a product service iteration apparatus provided in an embodiment of the present invention, where the apparatus may be implemented by software and/or hardware, and the apparatus may be integrated on an electronic device, where the electronic device may be a server (e.g., a gateway server) or a user terminal.
Referring to fig. 1, the method of the embodiment of the present invention specifically includes the following steps:
and S110, responding to the product service calling request, and determining product services to be called, wherein the product services are respectively deployed on at least two server clusters.
The product service invoking request may be a request initiated by a user terminal to invoke a certain product service deployed on the server cluster, where the product service is a product service to be invoked, such as an inquiry service, a storage service, or a modification service. It should be noted that, in order to ensure high availability of the product service, the product service may be previously deployed on at least two server clusters, and the product service invocation request only requests to invoke the product service, and does not specify to invoke the product service deployed on a certain server cluster.
In practical applications, optionally, the product service invocation request may be responded by a gateway service, where the gateway service may be a service deployed on a server (or a server cluster) outside of the at least two server clusters, or may also be a service respectively deployed on the at least two server clusters, and is not specifically limited herein. When the gateway service is deployed on at least two server clusters, which server cluster finally responds to the product service invocation request, or which server cluster receives the product service invocation request, may be determined by a preset load balancing algorithm.
And S120, determining a service-providing cluster from each server cluster according to the tangential flow configuration of the product service, wherein the service-providing cluster is used for providing the product service.
The cut-flow configuration may be a configuration that is set in advance for the product service to determine which one or more server clusters of the at least two server clusters are responsible for the online traffic (i.e., providing the product service), which may also be referred to as the production traffic. Therefore, a service providing cluster, i.e., a server cluster for providing the product service, may be determined from the server clusters according to the cut flow configuration.
S130, the product service calling request is forwarded to the product service deployed on the service lifting cluster so as to realize the calling process of the product service and the iteration process on the service stopping cluster, wherein the service stopping cluster is a cluster except the service lifting cluster in at least two server clusters, and the service stopping cluster stops providing the product service.
The service providing cluster is a server cluster which is responsible for the online flow of the product service, so that the received product service calling request can be forwarded to the product service deployed on the service providing cluster, and the calling process of the product service is realized. For example, since each product service provides a unique interface to the outside, the product service invocation request may be forwarded to the product service deployed on the offering cluster through the interface corresponding to the product service. It should be noted that, in such a cut-off configuration, each product service invocation request requesting to invoke the product service is forwarded to the serving cluster, which means that the off-line cluster of at least two server clusters except the serving cluster does not need to be responsible for the online traffic of the product service any more, i.e. the off-line cluster may be understood as a server cluster which stops providing the product service, so that the iterative process of the product service can be implemented on the off-line cluster.
Therefore, the above technical solution is to implement an iterative process of product services through a flow switching operation of product service dimensions, that is, when a certain product service is iterated, only all online flows of the product service are switched to the serving cluster of the product service, and as for the online flows of the remaining product services, the online flows of the remaining product services are switched to which server cluster, which is related to their respective flow switching configurations, that is, the online flows of all product services are not uniformly switched to the serving cluster. Therefore, even if a plurality of product services have iteration requirements in the same time period, the problems that the implementation efficiency of the iteration process is low because the product services need to be waited to be switched to another server cluster after the product services are issued and verified on a certain server cluster, and the iteration fails because the complex confirmation process is not executed in place are solved, and the implementation efficiency and the success rate of the iteration process of any product service are ensured.
In order to more visually understand the above iterative process of implementing product service through the cut flow operation of the product service dimension, the following provides an exemplary description of the cut flow configuration. When a research and development tester needs to iterate (i.e., update the version) a certain product service that has been deployed online, a cut-flow configuration of the product service can be set by one key on a developed product service cut-flow platform, and the cut-flow configuration can be represented by a mapping relationship such as appType: prd, where appType can represent a service identifier of the product service (i.e., represent the product service by the service identifier), and prd can represent a cluster identifier of a corresponding service-providing cluster (i.e., represent the service-providing cluster by the cluster identifier). It should be noted that, in the same time period, there may be a plurality of product services all having an iteration requirement, and the service-providing clusters respectively corresponding to the product services may be the same or different, which is the intuitive embodiment of implementing the cut-flow operation based on the product service dimension. Exemplarily, assuming that any product service is respectively deployed on two server clusters prd1 and prd, for three product services appType1, appType2 and appType3 with iterative requirements in the same time period, the cut-flow configurations set for them by the development tester are appType1: prd, appType2: prd and appType3: prd, respectively, which means that the on-line traffic of appType1 and appType2 is responsible by prd1, and the on-line traffic of appType3 is responsible by prd, the development tester can implement the new versions of appType1 and appType2 on the prd not responsible for the on-line traffic of appType1 and appType2, and implement the on-line traffic of appType 5364 zxft 533. Taking appType2 as an example, after the new version appType2 is released and verified on prd, the research and development tester can modify appType2: prd into appType2: prd2, so that prd2 is responsible for online traffic of appType2, and online deployment of the new version appType2 is realized on prd 1. The flow cutting process of the appType1 and the appType3 is similar, and is not described in detail herein.
From the above, compared with the iterative process of product service realized by the tangential flow operation of platform dimensions, the technical scheme does not need to rely on domain name resolution, thereby reducing the cost of domain name tangential flow resolution; the method isolates the influence of the tangential flow among the product services, and can perform the tangential flow online at any time according to the iteration requirement, thereby reducing the misoperation risk brought by unified tangential flow and improving the realization efficiency of the iteration process; and the flow switching operation is sunk to the gateway service from the domain name service, and the gateway service does not need to switch the flow back and forth according to the online rhythm of the product service.
According to the technical scheme of the embodiment of the invention, the product service to be called is determined by responding to the product service calling request, and in order to ensure the high availability of the product service, the product service is respectively deployed on at least two server clusters; determining a service providing cluster for providing the product service (namely, the online flow responsible for the product service) from each server cluster according to the flow switching configuration of the product service; the product service calling request is forwarded to the product service deployed on the service-providing cluster, so that the calling process of the product service is realized, and the service-stopping cluster except the service-providing cluster in at least two server clusters is no longer responsible for the online flow of the product service, so that the iterative process of the product service on the service-stopping cluster can be realized under the condition that a user does not perceive. According to the technical scheme, the iterative process of the product service is realized through the tangential flow operation of the product service dimension, so that the realization efficiency and the success rate of the iterative process are ensured.
An optional technical solution, determining a product service to be invoked may include: acquiring a service identifier of a product service to be called from the product service calling request, and determining the product service according to the service identifier; the product service iteration method may further include: and acquiring a pre-configured cut flow configuration set, and obtaining a cut flow configuration from the cut flow configuration set, wherein the cut flow configuration represents a mapping relation between the service identifier and the cluster identifier of the service providing cluster. The service identifier can be understood as a unique identifier of the product service, so that the product service can be uniquely determined according to the service identifier. The cut-flow configuration set may be a preset set including a plurality of candidate configurations, and each candidate configuration may indicate a mapping relationship between a certain service identifier and a cluster identifier of a certain server cluster, so that a cut-flow configuration related to the mapping relationship of the service identifier may be obtained from the cut-flow configuration set, thereby achieving an effect of quickly determining the cut-flow configuration.
In another optional technical solution, the product service iteration method may be applied to a gateway service, and the gateway service is respectively deployed on each server cluster; on this basis, the product service iteration method may further include: and if the tangent flow configuration is not obtained, taking the server cluster where the gateway service receiving the product service calling request is located as a service providing cluster. In practical application, relevant personnel can only set corresponding cut flow configuration for product services with iteration requirements, because product service call requests corresponding to product services without iteration can be processed by any server cluster, and the product service call requests fall into which server cluster, the product service call requests can be directly processed by the server cluster. In other words, after a gateway service deployed on a certain server cluster receives a product service call request, if the cut-flow configuration of the product service requested to be called is not obtained, the gateway service can directly serve as the server cluster where the gateway service is located, so that effective response of the product service call request corresponding to the product service with or without the iteration requirement is ensured.
Another optional technical solution, where the product service iteration method further includes: acquiring the cut flow configuration at regular time, and updating the cut flow configuration stored in the cache according to the cut flow configuration acquired at regular time; correspondingly, after determining the product service to be called, the product service iteration method may further include: and acquiring the cut flow configuration from the cache. In the product service iteration process, in order not to affect the normal application of a user to a product service with an iteration requirement, related personnel usually perform online deployment of the product service on a certain server cluster first, and then switch to another server cluster to perform online deployment of the product service, which means that the cut-flow configuration of the product service is not fixed. Therefore, the cut flow configuration can be obtained at regular time, and the cut flow configuration stored in the cache is updated based on the cut flow configuration obtained at regular time, namely the cut flow configuration obtained historically is updated, so that the cut flow configuration obtained from the cache subsequently is the latest cut flow configuration, and further the product service calling request of the service product is prevented from being forwarded to the server cluster which is deploying the product service on line, and therefore the iterative process of the product service on each server cluster is completed under the condition that a user does not perceive the product service. On this basis, optionally, the above-mentioned timing acquisition process may be understood as acquiring once every preset time length (e.g. 20 seconds), may also be understood as acquiring once at each preset time point, and the like, and is not specifically limited herein. Optionally, timing synchronization of the cut flow configuration of any product service may also be implemented based on the above technical solution, and is not limited to timing synchronization of a product service having an iteration requirement and/or a call requirement, so that it is ensured that the latest cut flow configuration of any product service can be obtained from a cache when the product service is iterated.
Before the embodiments of the present invention are described, an application scenario of the embodiments of the present invention is described as an example. Static resources which are rarely changed, such as js files or CSS files, are often involved in the product service, and can be directly stored in the product service; the static resources of the product service can be directly returned to the user terminal without returning the static resources, so that the obtaining speed of the user terminal for the static resources is increased. For the second case, the address of the CDN node where the static resource of each product service is located may be stored in the gateway service, but this way of maintaining the address through the gateway service increases the coupling between the product service and the gateway service, thereby causing the independent product service to lose the complete closed-loop capability; besides, although static resources change rarely, there is always a possibility of change, which means that addresses stored in the gateway service need to be modified and released at that time, and when such operations are too frequent, the overall stability of the platform is easily reduced. In order to solve the above problem, a product service iteration method in the following embodiments is proposed.
Fig. 2 is a flowchart of another product service iteration method provided in the embodiment of the present invention. The present embodiment is optimized based on the above technical solutions. In this embodiment, optionally, the production resource of the product service is stored on the first content distribution network node, and the first address of the first content distribution network node is configured within the product service; after determining the serving cluster from the server clusters, the product service iteration method may further include: acquiring a first address from a product service deployed on a service offering cluster; and returning the first address to the initiator of the product service calling request, so that the initiator acquires the production resource from the first content distribution network node corresponding to the received first address, and loads and renders the production resource. The same or corresponding terms as those in the above embodiments are not explained in detail herein.
Referring to fig. 2, the method of the present embodiment may specifically include the following steps:
s210, responding to the product service calling request, and determining product services to be called, wherein the product services are respectively deployed on at least two server clusters.
S220, determining a service-providing cluster from each server cluster according to the tangential flow configuration of the product service, wherein the service-providing cluster is used for providing the product service.
S230, the production resource of the product service is stored in the first content distribution network node, and the first address of the first content distribution network node is configured in the product service, and is obtained from the product service deployed on the service providing cluster.
A production resource is understood to be a static resource of an online formal application of a product service, which may also be referred to as a formal resource. The production resource is stored on a first CDN node and a first address of the first CDN node is configured within the product service. In other words, the first address corresponding to each product service is maintained by the product service itself. On the basis, for the product service to be called, the corresponding first address can be acquired from the product service deployed on the service providing cluster. In practical applications, optionally, the first address may be obtained through a resource loading interface.
S240, the first address is returned to the initiator of the product service calling request, so that the initiator acquires the production resource from the first content distribution network node corresponding to the received first address, and loads and renders the production resource.
The initiator may be an object for initiating a product service invocation request, such as the user terminal illustrated above. And returning the first address to the initiator, so that the initiator dynamically pulls the production resource from the first CDN node corresponding to the received first address, thereby realizing the loading and rendering of the production resource.
It should be noted that, when the static resource is changed, the iteration process of the static resource may also be implemented based on the product service iteration method described in each technical solution. Specifically, besides setting the cut-flow configuration of the product service to obtain the service-providing cluster, the relevant person may modify a first address configured in the product service deployed on the service-stopping cluster into a second address, where a second CDN node corresponding to the second address stores a grayscale resource (i.e., an updated production resource). Therefore, similar to the release verification of product services, the release verification can be performed on the gray level resource, and the iterative process of the static resource is realized.
And S250, forwarding the product service calling request to the product service deployed on the service-providing cluster to realize the calling process of the product service and the iteration process on the service-stopping cluster, wherein the service-stopping cluster is a cluster except the service-providing cluster in at least two server clusters, and the service-stopping cluster stops providing the product service.
It should be noted that S230 and S250 may be executed serially (for example, after S230 is executed, S250 is executed, or after S250 is executed, S230 is executed), or executed in parallel (that is, the execution processes of S230 and S250 do not interfere with each other), which is not limited herein.
According to the technical scheme of the embodiment of the invention, the production resource is split into the product service for maintenance through a dynamic loading mechanism of the production resource, namely, the address configuration is sunk to the product service from the gateway service, so that the dependence of the product service on the gateway service is eliminated, and the independent closed-loop development and deployment of the product service are realized; and the gateway service does not need to be configured and released according to the online rhythm of the product service, so that the daily online labor input of the gateway service is reduced, and the overall stability of the platform is improved.
On the basis, according to an optional technical scheme, the gray resources of the product service are stored in the second content distribution network node, the second address of the second content distribution network node is configured in the product service, and the gray resources are updated production resources; acquiring the first address from the product service deployed on the service offering cluster may include: if the gray resource request parameter is not obtained from the product service calling request, obtaining a first address from a product service deployed on a service providing cluster; after determining the serving cluster from the server clusters, the product service iteration method may further include: if the gray resource request parameter is obtained, obtaining a second address from a product service deployed on the service providing cluster; and returning the second address to the initiator so that the initiator acquires the gray resources from the second content distribution network node corresponding to the received second address and loads and renders the gray resources.
The gray level resource can be understood as an updated production resource, i.e., a static resource to be issued for verification. Similar to a production resource, the grayscale resource is stored on a second CDN node, and a second address of the second CDN node is configured within the product service. In other words, if a product service corresponds to a second address, then the second address is maintained by the product service itself. It should be noted that, in general, the first address and the second address are different addresses, that is, the first CDN node and the second CDN node are different CDN nodes, because if the first address and the second address are the same, that is, the grayscale resource covers the production resource, the user directly applies to the grayscale resource that has not been verified, and thus an online accident is easily caused.
In addition to the iterative process of static resources through a tangential flow operation of the product-service dimension set forth above, another alternative to the iterative process of static resources is presented here. Specifically, in order to distinguish a product service invocation request initiated by a user from a product service invocation request initiated by a related person (such as a research and development tester), the related person may additionally add a gray resource request parameter gradtag in the product service invocation request, that is, a parameter indicating that the request is a gray resource. Thus, after receiving the product service invocation request, it can be determined whether the gray resource request parameter is included therein. If not, this indication is user initiated, then the first address may be obtained from within a product service deployed on the customer care cluster. If the content includes the description that the content is originated by the related person, the second address may be obtained from the product service deployed on the service providing cluster, so as to return the second address to the initiator (for example, a user terminal operated by the related person), so that the initiator obtains the grayscale resource from the second CDN node corresponding to the received second address, thereby implementing loading and rendering of the grayscale resource. According to the technical scheme, whether the gray resource request parameter is obtained from the received product service calling request or not is judged, and therefore whether the first address or the second address is returned to the initiator is determined, normal application of a user to product service can be guaranteed, opposite personnel can be guaranteed to issue verification gray resources, the iteration process of static resources can be achieved without switching operation, and application convenience is high.
On this basis, optionally, the product service iteration method may further include: in response to the address override instruction, the first address is overridden based on the second address and the second address is deleted. That is, after the release verification of the gray level resource is passed, the first address configured in the product service is covered based on the second address configured in the product service, so that the user is ensured to apply the updated online resource (namely the gray level resource) when calling the product service; and, the second address configured within the product service is deleted.
Fig. 3 is a flow chart of another product service iteration method provided in the embodiment of the present invention. The present embodiment is optimized based on the above technical solutions. In this embodiment, optionally, the product service iteration method is applied to a gateway service, and the gateway service may be deployed on each server cluster respectively; moreover, production resources of the product service are stored on a first CDN node, a grayscale resource of the product service is stored on a second CDN node, the grayscale resource is an updated production resource, and both a first address of the first CDN node and a second address of the second CDN node are configured within the product service. The same or corresponding terms as those in the above embodiments are not explained in detail herein.
Referring to fig. 3, the method of this embodiment may specifically include the following steps:
s3010, responding to the product service calling request, obtaining a service identifier of the product service to be called from the product service calling request, and determining the product service according to the service identifier, wherein the product service is respectively deployed on at least two server clusters.
Wherein, each server cluster is deployed with both product service and gateway service. After receiving the product service calling request, the gateway service deployed on any server cluster responds to the product service calling request to acquire the service identifier of the product service to be called, and further determines the product service.
And S3020, acquiring the cut flow configuration set at regular time, and updating the cut flow configuration set stored in the cache according to the cut flow configuration set acquired at regular time.
It should be noted that, this step is a step executed at regular time, that is, the execution sequence of the step and the remaining steps is related to the actual situation, and is not limited in any way here.
S3030, acquiring the tangent flow configuration set from the cache.
S3040, if the flow switching configuration of the product service is obtained from the flow switching configuration set, determining a service lifting cluster from all the server clusters according to the flow switching configuration, wherein the flow switching configuration represents the mapping relation between the service identifier and the cluster identifier of the service lifting cluster.
S3050, if the flow cutting configuration is not obtained from the flow cutting configuration set, taking a server cluster where the gateway service receiving the product service calling request is located as a service extracting cluster, wherein the service extracting cluster is used for providing the product service.
S3060, if the gray resource request parameter is not obtained from the product service calling request, obtaining a first address from the product service deployed on the service providing cluster.
S3070, the first address is returned to the initiator of the product service calling request, so that the initiator acquires the production resource from the first CDN node corresponding to the received first address, and loads and renders the production resource.
S3080, if the gray resource request parameter is obtained, obtaining a second address from the product service deployed on the service providing cluster.
S3090, returning the second address to the initiator so that the initiator acquires the gray resource from the second CDN node corresponding to the received second address and loads and renders the gray resource.
And S3100, responding to the address covering instruction, covering the first address based on the second address, and deleting the second address to realize the iterative process of the production resources.
S3110, forwarding the product service call request to a product service deployed on a service-providing cluster to realize a call process of the product service and an iteration process on a service-stopping cluster, wherein the service-stopping cluster is a cluster of at least two server clusters except the service-providing cluster, and the service-stopping cluster stops providing the product service.
It should be noted that, taking S3060-S3070 branches as an example (similar to the case of S3080-S3090), the execution sequence of the branch and S3110 may be executed first or later, or may be executed in parallel, which is not specifically limited herein.
According to the technical scheme of the embodiment of the invention, the flow switching operation is sunk from the domain name service to the gateway service, so that the flow switching operation of product service dimensionality is realized, and the realization efficiency and success rate of the iterative process of product service are ensured; in addition, by sinking the address configuration from the gateway service to the product service, independent closed-loop development and deployment of the product service are realized, and the overall stability of the platform is improved.
In order to better understand the technical solution, the following description is made by way of example with reference to specific examples. Illustratively, referring to fig. 4, the cut-flow operation of the product service dimension is illustrated here, still taking the SAAS platform in the above example as an example. In particular, the method comprises the following steps of,
1. introducing a product service flow switching platform to support research and development testers to set flow switching configuration for product services with iteration requirements on the product service flow switching platform to obtain a flow switching configuration set, wherein the flow switching configuration set can be stored in a database by the product service flow switching service;
2. the gateway services deployed in each cluster respectively pull the cut flow configuration sets at regular time, and store the pulled cut flow configuration sets in a local cache of the gateway services, so that the synchronization of the cut flow configuration sets is realized;
3. after a user accesses www.xxx.com through a browser, the platform transfers a corresponding product service call request to a gateway service deployed under a certain cluster (such as a main cluster or a standby cluster) based on a balanced load algorithm, and the gateway service executes the following steps: if the cut flow configuration is obtained from the cut flow configuration set stored in the local cache according to the appType in the received product service calling request, determining whether the main cluster or the standby cluster is used as a service providing cluster according to the cut flow configuration; otherwise, this indicates that the product service corresponding to the appType (here, taking the product service a as an example) does not have an iteration requirement, and the cluster where the gateway service is located may be used as a serving cluster;
4. the gateway service forwards the product service calling request to the product service A deployed on the service-providing cluster through an interface externally provided by the product service A, so that the calling process of the product service A and the iteration process on the service-stopping cluster are realized, and the dynamic switching of the product service A is realized.
On this basis, if some static resources of the a product service are stored on the CDN node, the flow cutting process of the static resources can be implemented through the following steps. In particular, the method comprises the following steps of,
1. configuring a first address of a first CDN node where a production resource corresponding to the static resource is located and a second address of a second CDN node where a corresponding gray level resource is located in the product service A;
2. the gateway service determines whether the received product service call request contains a grayTag, if so, the gateway service acquires a first address from the product service A based on a resource loading interface and returns the first address to the browser, so that the browser acquires a production resource from a first CDN node corresponding to the received first address and loads and renders the production resource, and a user can browse the production resource; otherwise, acquiring a second address from the product service A based on the resource loading interface, and returning the second address to the browser, so that the browser acquires the gray resource from a second CDN node corresponding to the received second address, and loads and renders the gray resource, and research and development testers can verify the gray resource;
3. after the verification is completed, the first address can be overwritten based on the second address configured in the product A service, so that the formal release of the static resource is completed.
Fig. 5 is a block diagram of a product service iteration apparatus according to an embodiment of the present invention, which is configured to execute a product service iteration method according to any of the above embodiments. The product service iteration method of the device and the product service iteration methods of the embodiments belong to the same inventive concept, and reference may be made to the embodiments in the product service iteration method for details that are not described in detail in the embodiments of the product service iteration device. Referring to fig. 5, the apparatus may specifically include: a product service determination module 410, a mention cluster determination module 420, and a product service iteration module 430. Wherein the content of the first and second substances,
a product service determining module 410, configured to determine, in response to a product service invocation request, product services to be invoked, where the product services are respectively deployed on at least two server clusters;
a service-offering cluster determining module 420, configured to determine a service-offering cluster from each server cluster according to a tangential flow configuration of a product service, where the service-offering cluster is used for providing the product service;
and the product service iteration module 430 is configured to forward the product service call request to a product service deployed on the service providing cluster, so as to implement a call process of the product service and an iteration process on a service stopping cluster, where the service stopping cluster is a cluster other than the service providing cluster in the at least two server clusters, and the service stopping cluster stops providing the product service.
Optionally, the product service determination module 410 may include:
the product service determining unit is used for acquiring a service identifier of the product service to be called from the product service calling request and determining the product service according to the service identifier;
the product service iteration device may further include:
and the flow switching configuration obtaining module is used for obtaining a pre-configured flow switching configuration set and obtaining flow switching configuration from the flow switching configuration set, wherein the flow switching configuration represents the mapping relation between the service identifier and the cluster identifier of the service providing cluster.
Optionally, the product service iteration device is configured to a gateway service, and the gateway service is respectively deployed on each server cluster;
the product service iteration device may further include:
and the service-lifting cluster obtaining module is used for taking the server cluster where the gateway service receiving the product service calling request is located as a service-lifting cluster if the cut-flow configuration is not obtained.
Optionally, the product service iteration apparatus may further include:
the switching configuration updating module is used for acquiring the switching configuration at regular time and updating the switching configuration stored in the cache according to the switching configuration acquired at regular time;
and the cut flow configuration acquisition module is used for acquiring the cut flow configuration from the cache after determining the product service to be called.
Optionally, the production resources of the product service are stored on a first content distribution network node, and a first address of the first content distribution network node is configured within the product service;
the product service iteration device may further include:
the first address acquisition module is used for acquiring a first address from product services deployed on the service providing cluster after the service providing cluster is determined from each server cluster;
and the production resource rendering module is used for returning the first address to the initiator of the product service calling request so that the initiator acquires the production resource from the first content distribution network node corresponding to the received first address and loads and renders the production resource.
On this basis, optionally, the grayscale resource of the production service may be stored on the second content distribution network node, and the second address of the second content distribution network node may be configured within the production service, the grayscale resource being an updated production resource;
the first address obtaining module may include:
the first address obtaining unit is used for obtaining a first address from the product service deployed on the service providing cluster if the gray resource request parameter is not obtained from the product service calling request;
the product service iteration device may further include:
the second address acquisition module is used for acquiring a second address from a product service deployed on the service providing cluster if the gray resource request parameter is acquired after the service providing cluster is determined from each server cluster;
and the gray resource rendering module is used for returning the second address to the initiator so that the initiator acquires the gray resource from the second content distribution network node corresponding to the received second address and loads and renders the gray resource.
On this basis, optionally, the product service iteration apparatus may further include:
and the second address deleting module is used for responding to the address covering instruction, covering the first address based on the second address and deleting the second address.
The product service iteration device provided by the embodiment of the invention responds to a product service calling request through the product service determining module to determine the product service to be called, and can be respectively deployed on at least two server clusters in order to ensure the high availability of the product service; determining a service-offering cluster for providing the product service (namely the online flow which is responsible for the product service) from each server cluster through a service-offering cluster determining module according to the cut-flow configuration of the product service; the product service calling request is forwarded to the product service deployed on the service-providing cluster through the product service iteration module, so that the calling process of the product service is realized, and the service-stopping clusters except the service-providing cluster in the at least two server clusters are no longer responsible for the online flow of the product service, so that the iteration process of the product service on the service-stopping clusters can be realized under the condition that a user does not perceive the product service. The device realizes the iterative process of the product service through the tangential flow operation of the product service dimension, thereby ensuring the realization efficiency and the success rate of the iterative process.
The product service iteration device provided by the embodiment of the invention can execute the product service iteration method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
It should be noted that, in the embodiment of the product service iteration apparatus, each included unit and each included module are only divided according to functional logic, but are not limited to the above division, as long as corresponding functions can be implemented; in addition, the specific names of the functional units are only for the convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
FIG. 6 illustrates a schematic structural diagram of an electronic device 10 that may be used to implement an embodiment of the present invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 6, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, and the like, wherein the memory stores a computer program executable by the at least one processor, and the processor 11 can perform various suitable actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from a storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data necessary for the operation of the electronic apparatus 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to the bus 14.
A number of components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, or the like; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.
The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, or the like. The processor 11 performs the various methods and processes described above, such as the product service iteration method.
In some embodiments, the product-service iteration method may be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the product-service iteration method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the product-service iteration method by any other suitable means (e.g., by way of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. A computer program can execute entirely on a machine, partly on a machine, as a stand-alone software package partly on a machine and partly on a remote machine or entirely on a remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired results of the technical solution of the present invention can be achieved.
The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A product-service iteration method, comprising:
responding to a product service calling request, and determining product services to be called, wherein the product services are respectively deployed on at least two server clusters;
determining an extraction cluster from each server cluster according to the tangential flow configuration of the product service, wherein the extraction cluster is used for providing the product service;
forwarding the product service calling request to the product service deployed on the service-providing cluster to realize a calling process of the product service and an iterative process on a service-stopping cluster, wherein the service-stopping cluster is a cluster of the at least two server clusters except the service-providing cluster, and the service-stopping cluster stops providing the product service.
2. The method of claim 1, wherein determining the product service to be invoked comprises:
acquiring a service identifier of a product service to be called from the product service calling request, and determining the product service according to the service identifier;
the method further comprises the following steps:
and acquiring a pre-configured flow cut configuration set, and obtaining the flow cut configuration from the flow cut configuration set, wherein the flow cut configuration represents a mapping relation between the service identifier and the cluster identifier of the service providing cluster.
3. The method of claim 1, applied to a gateway service deployed on each of the server clusters;
the method further comprises the following steps:
and if the flow switching configuration is not obtained, the server cluster where the gateway service receiving the product service calling request is located is used as the service lifting cluster.
4. The method of claim 1, further comprising:
acquiring the cut flow configuration at regular time, and updating the cut flow configuration stored in a cache according to the cut flow configuration acquired at regular time;
after the determining the product service to be invoked, the method further comprises:
and acquiring the cut flow configuration from the cache.
5. The method of claim 1, wherein production resources of the production service are stored on a first content distribution network node, and a first address of the first content distribution network node is configured within the production service;
after the determining of the serving cluster from the server clusters, the method further comprises:
acquiring the first address from the product service deployed on the service providing cluster;
and returning the first address to the initiator of the product service calling request, so that the initiator acquires the production resource from the first content distribution network node corresponding to the received first address, and loads and renders the production resource.
6. The method of claim 5, wherein a grayscale resource of the production service is stored on a second content distribution network node, and a second address of the second content distribution network node is configured within the production service, the grayscale resource being the updated production resource;
the obtaining the first address from the product service deployed on the offering cluster comprises:
if the gray resource request parameter is not obtained from the product service calling request, obtaining the first address from the product service deployed on the service providing cluster;
after the determining of the serving cluster from the server clusters, the method further comprises:
if the gray resource request parameter is obtained, obtaining the second address from the product service deployed on the service providing cluster;
and returning the second address to the initiator, so that the initiator acquires the gray resource from the second content distribution network node corresponding to the received second address, and loads and renders the gray resource.
7. The method of claim 6, further comprising:
and responding to an address covering instruction, covering the first address based on the second address, and deleting the second address to realize the iterative process of the production resource.
8. A product-service iterating apparatus, comprising:
the system comprises a product service determining module, a product service calling module and a product service calling module, wherein the product service determining module is used for responding to a product service calling request and determining a product service to be called, and the product service is respectively deployed on at least two server clusters;
an extraction cluster determining module, configured to determine an extraction cluster from each server cluster according to a tangential flow configuration of the product service, where the extraction cluster is used to provide the product service;
and the product service iteration module is used for forwarding the product service calling request to the product service deployed on the service-providing cluster so as to realize the calling process of the product service and the iteration process on a service-stopping cluster, wherein the service-stopping cluster is a cluster except the service-providing cluster in the at least two server clusters, and the service-stopping cluster stops providing the product service.
9. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to cause the at least one processor to perform the product-service iteration method of any of claims 1-7.
10. A computer-readable storage medium storing computer instructions for causing a processor to perform the product-service iteration method of any one of claims 1-7 when executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211542152.5A CN115756806A (en) | 2022-12-02 | 2022-12-02 | Product service iteration method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211542152.5A CN115756806A (en) | 2022-12-02 | 2022-12-02 | Product service iteration method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115756806A true CN115756806A (en) | 2023-03-07 |
Family
ID=85343051
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211542152.5A Pending CN115756806A (en) | 2022-12-02 | 2022-12-02 | Product service iteration method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115756806A (en) |
-
2022
- 2022-12-02 CN CN202211542152.5A patent/CN115756806A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109245908B (en) | Method and device for switching master cluster and slave cluster | |
| CN111460129A (en) | Method and device for generating identification, electronic equipment and storage medium | |
| CN115840956A (en) | File processing method, device, server and medium | |
| CN112671892B (en) | Data transmission method, device, electronic equipment and medium | |
| CN113541987A (en) | Method and device for updating configuration data | |
| CN117149248A (en) | Micro front end construction method, device, equipment and storage medium | |
| CN116545905A (en) | Service health detection method and device, electronic equipment and storage medium | |
| CN114070889B (en) | Configuration method, traffic forwarding device, storage medium, and program product | |
| CN112052152A (en) | Simulation test method and device | |
| CN115756806A (en) | Product service iteration method and device, electronic equipment and storage medium | |
| CN113076343B (en) | Data query method, device, equipment and storage medium | |
| CN114896317A (en) | Data structure conversion method and device, electronic equipment and storage medium | |
| CN115309730A (en) | Data auditing method and device, electronic equipment and storage medium | |
| CN112965836A (en) | Service control method and device, electronic equipment and readable storage medium | |
| CN113360689A (en) | Image retrieval system, method, related device and computer program product | |
| CN113220576B (en) | Management method, device, equipment and storage medium of test environment | |
| CN116668532A (en) | Data communication method, device, electronic equipment and storage medium | |
| CN116775171A (en) | Architecture switching method and device, electronic equipment and storage medium | |
| CN115617454A (en) | Containerization service deployment method, device, equipment and storage medium | |
| CN114647634A (en) | Method for creating database, method and device for operating database | |
| CN117298599A (en) | Game version scheduling method, system, equipment and storage medium | |
| CN117609161A (en) | File management method and device based on kubernetes, electronic equipment and storage medium | |
| CN117255100A (en) | Data synchronization method and device, electronic equipment and readable storage medium | |
| CN117234751A (en) | Cross-partition process communication method and device, electronic equipment and storage medium | |
| CN114896322A (en) | JSON (Java Server object notation) -based configuration data conversion method, device, equipment and 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 |