CN115225638B - Service deployment method, device, electronic equipment and computer readable storage medium - Google Patents
Service deployment method, device, electronic equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN115225638B CN115225638B CN202210860784.XA CN202210860784A CN115225638B CN 115225638 B CN115225638 B CN 115225638B CN 202210860784 A CN202210860784 A CN 202210860784A CN 115225638 B CN115225638 B CN 115225638B
- Authority
- CN
- China
- Prior art keywords
- service
- service gateway
- gateway
- instance
- service instance
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1044—Group management mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
- H04L67/1078—Resource delivery mechanisms
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Theoretical Computer Science (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application relates to the technical field of cloud deployment, and provides a service deployment method, a device, electronic equipment and a computer readable storage medium, wherein the method comprises the following steps: acquiring a service deployment request; distributing the flow of the cluster network to a first service gateway according to the service deployment request; then, deploying the second service gateway and the second back-end service instance; after the deployment of the second service gateway and the second back-end service instance is completed, distributing the traffic of the cluster network to the second service gateway and enabling the first back-end service instance to be in a maintenance state; then, deploying the first service gateway and the first back-end service instance; after deployment is completed, traffic of the clustered network is redistributed to the first service gateway and the second service gateway. By the technical scheme, the problem of task loss or service interruption caused by service deployment can be avoided.
Description
Technical Field
The embodiment of the application relates to the technical field of cloud deployment, but is not limited to, in particular to a service deployment method, a device, electronic equipment and a computer readable storage medium.
Background
In the service deployment scheme of the current remote procedure call (Remote Procedure Call, RPC) architecture, a back-end service instance needs to be registered to a distributed coordination service node for a gateway service to perform discovery call; in the actual production deployment process, when the back-end service instance needs deployment, the gateway service cannot be refused to be invoked; when the back-end service instance has tasks being executed, the tasks executed by the back-end service instance may be lost, so that other related service call exceptions are caused.
Disclosure of Invention
The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.
In order to solve the problems mentioned in the background art, embodiments of the present application provide a service deployment method, apparatus, electronic device, and computer readable storage medium, which can avoid the problem of task loss or service interruption caused by service deployment.
In a first aspect, an embodiment of the present application provides a service deployment method, applied to a trunking network, where the trunking network includes a first service gateway, a second service gateway, a first back-end service instance and a second back-end service instance, the first back-end service instance is in data connection with the first service gateway, and the second back-end service instance is in data connection with the second service gateway, and the service deployment method includes:
Acquiring a service deployment request;
distributing the traffic of the cluster network to the first service gateway according to the service deployment request and enabling the second back-end service instance to be in a maintenance state;
under the condition that the second service gateway and the second back-end service instance do not have task execution, deploying the second service gateway and the second back-end service instance;
after the second service gateway and the second back-end service instance are deployed, distributing traffic of the clustered network to the second service gateway and enabling the first back-end service instance to be in a maintenance state;
under the condition that the first service gateway and the first back-end service instance do not have task execution, the first service gateway and the first back-end service instance are deployed;
and after the first service gateway and the first back-end service instance are deployed, redistributing the traffic of the cluster network to the first service gateway and the second service gateway.
The service deployment method according to the embodiment provided by the application has at least the following beneficial effects: firstly, acquiring a service deployment request; distributing the traffic of the cluster network to a first service gateway according to the service deployment request and enabling the second back-end service instance to be in a maintenance state; under the condition that the second service gateway and the second back-end service instance do not have task execution, the second service gateway and the second back-end service instance are deployed; then after the second service gateway and the second back-end service instance are deployed, distributing the traffic of the cluster network to the second service gateway and enabling the first back-end service instance to be in a maintenance state; then, under the condition that the first service gateway and the first back-end service instance do not have task execution, the first service gateway and the first back-end service instance are deployed; and finally, after the first service gateway and the first back-end service instance are deployed, redistributing the traffic of the cluster network to the first service gateway and the second service gateway. Through the technical scheme, service deployment is performed according to the execution conditions of the service gateway and the back-end service instance, so that the service deployment can be performed only when the service gateway and the back-end service instance do not have task execution, and the problem of task loss or service interruption caused by service deployment can be avoided.
According to some embodiments of the application, the cluster network further includes a remote dictionary service Redis database, the first service gateway and the second service gateway are both in data connection with the Redis database, and the deploying the second service gateway and the second backend service instance in a case that neither the second service gateway nor the second backend service instance performs tasks includes:
inquiring the Redis database based on the first service gateway to obtain first working state information corresponding to the second service gateway and second working state information corresponding to the second back-end service instance;
and deploying the second service gateway and the second back-end service instance under the condition that the first working state information indicates that the second service gateway does not execute tasks and the second working state information indicates that the second back-end service instance does not execute tasks.
According to some embodiments of the application, after the deployment of the second service gateway and the second backend service instance is completed, distributing traffic of the clustered network to the second service gateway and placing the first backend service instance in a maintenance state includes:
After the second service gateway and the second back-end service instance are deployed, verifying the second service gateway and the second back-end service instance;
and distributing the traffic of the cluster network to the second service gateway and enabling the first back-end service instance to be in a maintenance state under the condition that the second service gateway and the second back-end service instance are successfully verified.
According to some embodiments of the application, the deploying the first service gateway and the first backend service instance without performing tasks on both the first service gateway and the first backend service instance includes:
inquiring the Redis database based on the second service gateway to obtain third working state information corresponding to the first service gateway and fourth working state information corresponding to the first back-end service instance;
and deploying the first service gateway and the first back-end service instance under the condition that the third working state information indicates that the first service gateway does not execute tasks and the fourth working state information indicates that the first back-end service instance does not execute tasks.
According to some embodiments of the application, after the deployment of the first service gateway and the first backend service instance is completed, redistributing the traffic of the clustered network to the first service gateway and the second service gateway includes:
after the first service gateway and the first back-end service instance are deployed, verifying the first service gateway and the first back-end service instance;
and under the condition that the first service gateway and the first back-end service instance are successfully verified, redistributing the traffic of the cluster network to the first service gateway and the second service gateway.
According to some embodiments of the application, the cluster network further includes a domain name server, the first service gateway and the second service gateway are both in data connection with the domain name server, and the distributing traffic of the cluster network to the first service gateway according to the service deployment request includes:
analyzing and processing the service deployment request based on the domain name server to obtain a flow distribution strategy;
and distributing the traffic of the cluster network to the first service gateway based on the traffic distribution policy.
According to some embodiments of the application, after the deploying the second service gateway and the second backend service instance, if the first working state information indicates that the second service gateway has no task to perform and the second working state information indicates that the second backend service instance has no task to perform, the deploying further includes:
and writing the name of the second back-end service instance into the Redis database.
In a second aspect, an embodiment of the present application further provides a service deployment apparatus, where the apparatus includes:
the first processing module is used for acquiring a service deployment request;
the second processing module is used for distributing the traffic of the cluster network to the first service gateway according to the service deployment request and enabling the second back-end service instance to be in a maintenance state;
the third processing module is used for deploying the second service gateway and the second back-end service instance under the condition that the second service gateway and the second back-end service instance do not have task execution;
a fourth processing module, configured to distribute, after deployment of both the second service gateway and the second backend service instance is completed, traffic of the clustered network to the second service gateway and cause the first backend service instance to be in a maintenance state;
A fifth processing module, configured to deploy the first service gateway and the first backend service instance when no task is executed by the first service gateway and the first backend service instance;
and the sixth processing module is used for redistributing the traffic of the cluster network to the first service gateway and the second service gateway after the first service gateway and the first back-end service instance are deployed.
In a third aspect, an embodiment of the present application further provides an electronic device, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the service deployment method as described in the first aspect above when executing the computer program.
In a fourth aspect, embodiments of the present application further provide a computer-readable storage medium storing computer-executable instructions for performing the service deployment method according to the first aspect above.
Additional features and advantages of the application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the application. The objectives and other advantages of the application will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
The accompanying drawings are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate and do not limit the application.
FIG. 1 is a network architecture diagram for performing a service deployment method provided by one embodiment of the present application;
FIG. 2 is a flow chart of a service deployment method provided by one embodiment of the present application;
FIG. 3 is a specific flowchart for deploying a service gateway and a backend service instance in a service deployment method according to an embodiment of the present application;
FIG. 4 is a flowchart illustrating verification of service deployment in a service deployment method according to an embodiment of the present application;
FIG. 5 is a specific flowchart for deploying a service gateway and a backend service instance in a service deployment method according to another embodiment of the present application;
FIG. 6 is a flowchart for verifying service deployment in a service deployment method according to another embodiment of the present application;
FIG. 7 is a flow chart of traffic distribution in a service deployment method according to an embodiment of the present application;
FIG. 8 is a flowchart of a backend service instance writing database in a service deployment method provided by one embodiment of the present application;
FIG. 9 is a schematic diagram of a service deployment apparatus provided by one embodiment of the present application;
fig. 10 is a schematic diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
It should be noted that although functional block division is performed in the apparatus schematic and logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than block division in the apparatus or in the flowchart. The terms first, second and the like in the description and in the claims and in the above-described figures, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
It is to be noted that all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs unless defined otherwise. The terminology used herein is for the purpose of describing embodiments of the application only and is not intended to be limiting of the application.
The application provides a service deployment method, a device, electronic equipment and a computer readable storage medium, wherein a service deployment request is firstly acquired; distributing the traffic of the cluster network to a first service gateway according to the service deployment request and enabling the second back-end service instance to be in a maintenance state; under the condition that the second service gateway and the second back-end service instance do not have task execution, the second service gateway and the second back-end service instance are deployed; then after the second service gateway and the second back-end service instance are deployed, distributing the traffic of the cluster network to the second service gateway and enabling the first back-end service instance to be in a maintenance state; then, under the condition that the first service gateway and the first back-end service instance do not have task execution, the first service gateway and the first back-end service instance are deployed; and finally, after the first service gateway and the first back-end service instance are deployed, redistributing the traffic of the cluster network to the first service gateway and the second service gateway. Through the technical scheme, service deployment is performed according to the execution condition of the back-end service instance, so that the problem of task loss or service interruption caused by service deployment can be avoided.
The embodiment of the application provides a service deployment method, which relates to the technical field of cloud deployment. The service deployment method provided by the embodiment of the application can be applied to the terminal, can be applied to the server side, and can also be software running in the terminal or the server side. In some embodiments, the terminal may be a smart phone, tablet, notebook, desktop, etc.; the server side can be configured as an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, and a cloud server for providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, basic cloud computing services such as big data and artificial intelligent platforms and the like; the software may be an application or the like that implements the service deployment method, but is not limited to the above form.
The application is operational with numerous general purpose or special purpose computer system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
In the embodiments of the present application, when related processing is performed according to user information, user behavior data, user history data, user location information, and other data related to user identity or characteristics, permission or consent of the user is obtained first, and the collection, use, processing, and the like of the data comply with related laws and regulations and standards of related countries and regions. In addition, when the embodiment of the application needs to acquire the sensitive personal information of the user, the independent permission or independent consent of the user is acquired through popup or jump to a confirmation page and the like, and after the independent permission or independent consent of the user is definitely acquired, the necessary relevant data of the user for enabling the embodiment of the application to normally operate is acquired.
Embodiments of the present application will be further described below with reference to the accompanying drawings.
As shown in fig. 1, fig. 1 is a schematic diagram of a network architecture for performing a service deployment method according to an embodiment of the present application. In the example of fig. 1, the network architecture includes a domain name server, a first service gateway, a second service gateway, a first back-end service instance, a second back-end service instance, and a remote dictionary service dis database; the first service gateway and the second service gateway are both connected with the domain name server in a data mode, the first service gateway and the second service gateway are both connected with the Redis database in a data mode, the first back-end service instance is connected with the first service gateway in a data mode, and the second back-end service instance is connected with the second service gateway in a data mode.
It should be noted that at least one domain name server is used for performing data connection and forwarding with external network; at least two service gateways exist in the network architecture, in the embodiment of the present application, only two cases are listed, and it should not be considered that only two service gateways exist in the network architecture of the present application; the back-end service instance connected with a service gateway is also more than one; in the embodiment of the application, only the simplest case is listed, namely, only one back-end service instance connected to the same service gateway in the network architecture is listed, which is only one case provided by the embodiment of the application, and it should not be considered that only one back-end service instance connected to the same service gateway is provided, and there may be a plurality of back-end service instances connected to the same service gateway.
It should be noted that the first and second described in the embodiments of the present application are merely used to distinguish different objects, so that the relationship between different objects may be more clearly explained, and the described objects should not be considered as belonging to different types of objects, for example, for the first service gateway and the second service gateway, both may be the same type of gateway.
The network architecture and the application scenario described in the embodiments of the present application are for more clearly describing the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided by the embodiments of the present application, and those skilled in the art can know that, with the evolution of the network architecture and the appearance of the new application scenario, the technical solution provided by the embodiments of the present application is applicable to similar technical problems.
It will be appreciated by those skilled in the art that the network architecture shown in fig. 1 is not limiting of the embodiments of the application and may include more or fewer components than shown, or certain components may be combined, or a different arrangement of components.
Based on the structure of the network architecture, various embodiments of the service deployment method of the present application are presented.
As shown in fig. 2, fig. 2 is a flowchart of a service deployment method according to an embodiment of the present application. The method is applied to a cluster network, the cluster network comprises a first service gateway, a second service gateway, a first back-end service instance and a second back-end service instance, the first back-end service instance is in data connection with the first service gateway, the second back-end service instance is in data connection with the second service gateway, and the service deployment method comprises, but is not limited to, steps S100, S200, S300, S400, S500 and S600:
Step S100, obtaining a service deployment request;
step S200, distributing the flow of the cluster network to a first service gateway according to the service deployment request and enabling a second back-end service instance to be in a maintenance state;
step S300, under the condition that the second service gateway and the second back-end service instance do not have task execution, the second service gateway and the second back-end service instance are deployed;
step S400, after the second service gateway and the second back-end service instance are deployed, distributing the traffic of the cluster network to the second service gateway and enabling the first back-end service instance to be in a maintenance state;
step S500, under the condition that the first service gateway and the first back-end service instance do not have task execution, the first service gateway and the first back-end service instance are deployed;
in step S600, after the deployment of both the first service gateway and the first backend service instance is completed, the traffic of the clustered network is redistributed to the first service gateway and the second service gateway.
It should be noted that, firstly, a service deployment request is obtained; distributing the traffic of the cluster network to a first service gateway according to the service deployment request and enabling the second back-end service instance to be in a maintenance state; under the condition that the second service gateway and the second back-end service instance do not have task execution, the second service gateway and the second back-end service instance are deployed; then after the second service gateway and the second back-end service instance are deployed, distributing the traffic of the cluster network to the second service gateway and enabling the first back-end service instance to be in a maintenance state; then, under the condition that the first service gateway and the first back-end service instance do not have task execution, the first service gateway and the first back-end service instance are deployed; and finally, after the first service gateway and the first back-end service instance are deployed, redistributing the traffic of the cluster network to the first service gateway and the second service gateway. Through the technical scheme, service deployment is performed according to the execution condition of the back-end service instance, so that the problem of task loss or service interruption caused by service deployment can be avoided.
It should be noted that, under the condition that the second service gateway and the second backend service instance do not have tasks to execute, the second service gateway and the second backend service instance are deployed; the second service gateway and the second back-end service instance are deployed, namely, relevant source codes are generated into an executable software package, the executable software package is placed on target environments of the second service gateway and the second back-end service instance, and finally, the target environments are configured to enable the software package to normally operate, so that the deployment of the second service gateway and the second back-end service instance can be completed. Similarly, the deployment of the first service gateway and the first back-end service instance can also be performed by the deployment mode.
It should be noted that a clustered network is a group of computers that as a whole provide a user with a set of network resources, and these individual computer systems are nodes of the cluster. Clusters provide the following key features; the expandability, the performance of the cluster is not limited to a single service entity, and a new service entity can be dynamically added into the cluster, so that the performance of the cluster is enhanced; the high availability, the cluster avoids the client from easily encountering the warning of no service through the redundancy of the service entity, when one node server fails, the application program running on the server is automatically taken over on the other node server, and the elimination of single-point failure is very important for enhancing the availability, the accessibility and the reliability of data; load balancing, which can uniformly distribute tasks to computing and network resources in a cluster environment so as to improve data throughput; error recovery, if a certain server in the cluster is unavailable due to failure or maintenance requirement, the resources and the application programs are transferred to the available cluster nodes, and the process that the resources in one node can transparently take over and continue to complete tasks is called error recovery because the resources in the other available node cannot work.
It should be noted that, the service gateway includes a route forwarding and a filter, where the route forwarding is used to receive all external requests and forward the external requests to the micro service at the back end; the filter is used to perform a series of cross-cut functions in the service gateway, such as rights verification, throttling, and monitoring, all of which may be performed by the filter.
It should be noted that, the back-end service instance is an object operated by the service instance, and is configured and managed by the service; the service instance may be viewed in service details, wherein when the instance is running abnormally, the instance state may display relevant anomaly information.
It is noted that, in the embodiment of the present application, the first service gateway is configured to perform call processing on the first back-end service instance, and the second service gateway is configured to perform call processing on the second back-end service instance; in the deployment process, the traffic of the cluster network is distributed to one service gateway, and service deployment is performed when the other service gateway and the related back-end service instance do not have task execution, so that the problem of task loss or service interruption caused by service deployment can be avoided, and the service deployment process is more reliable.
It should be noted that, the back-end service instance is placed in the maintenance state, so that the back-end service instance does not execute a new task, and after the back-end service instance completes the task, a subsequent service deployment operation is performed.
In some embodiments, as shown in fig. 3, the cluster network further includes a remote dictionary service Redis database, and the first service gateway and the second service gateway are both in data connection with the Redis database, where the step S300 may include, but is not limited to, steps S310 to S320.
Step S310, inquiring the Redis database based on the first service gateway to obtain first working state information corresponding to the second service gateway and second working state information corresponding to the second back-end service instance;
step S320, where the first working state information indicates that the second service gateway does not perform tasks and the second working state information indicates that the second backend service instance does not perform tasks, deploying the second service gateway and the second backend service instance.
It should be noted that, the first service gateway and the second service gateway are both connected with the Redis database, and the Redis database stores the working state information of each service gateway and each back-end service instance; in the service deployment process, a Redis database is firstly queried based on a first service gateway to obtain first working state information corresponding to a second service gateway and second working state information corresponding to a second back-end service instance; and under the condition that the first working state information indicates that the second service gateway does not execute tasks and the second working state information indicates that the second back-end service instance does not execute tasks, deploying the second service gateway and the second back-end service instance to realize deployment processing of the second service gateway and the second back-end service instance.
Notably, the Redis database is an open-source NoSQL database written in the C language; it supports master-slave synchronization, data can be synchronized from a master server to any number of slave servers, which can be master servers associated with other slave servers, which allows Redis to perform single-level tree replication; the storage disk can write data intentionally and unintentionally; the publishing/subscribing mechanism is fully realized, so that when the slave database synchronizes the tree anywhere, one channel can be subscribed to and the complete message publishing record of the master server is received, and the synchronization is helpful to the expandability of the reading operation and the data redundancy.
It may be appreciated that, when the first working state information indicates that the second service gateway does not perform any task and the second working state information indicates that the second backend service instance does not perform any task, that is, the first working state information indicates that the second service gateway does not perform any task, which is suitable for performing a subsequent service deployment operation, the second working state information indicates that the second backend service instance does not perform any task, which is suitable for performing a subsequent service deployment operation.
In some embodiments, as shown in fig. 4, the step S400 may include, but is not limited to, steps S410 to S420.
Step S410, after the deployment of the second service gateway and the second back-end service instance is completed, performing verification processing on the second service gateway and the second back-end service instance;
step S420, in the case that the second service gateway and the second backend service instance are both verified successfully, distributing the traffic of the clustered network to the second service gateway and making the first backend service instance in a maintenance state.
After the second service gateway and the second back-end service instance are deployed, verification processing can be performed on the second service gateway and the second back-end service instance; after the second service gateway and the second back-end service instance are successfully verified, the traffic of the cluster network is distributed to the second service gateway, the first back-end service instance is in a maintenance state, no new task is executed, and preconditions are prepared for subsequent service deployment.
It should be noted that, after the second service gateway and the second backend service instance are deployed, verification is further required to be performed on the second service gateway and the second backend service instance so as to detect the service deployment situation; and when the second service gateway and the second back-end service instance are verified successfully, distributing the traffic of the cluster network to the second service gateway and enabling the first back-end service instance to be in a maintenance state so as to realize subsequent service deployment operation.
In some embodiments, as shown in fig. 5, the step S500 may include, but is not limited to, steps S510 to S520.
Step S510, inquiring the Redis database based on the second service gateway to obtain third working state information corresponding to the first service gateway and fourth working state information corresponding to the first back-end service instance;
in step S520, the first service gateway and the first back-end service instance are deployed when the third operating state information indicates that the first service gateway has no task to execute and the fourth operating state information indicates that the first back-end service instance has no task to execute.
It should be noted that, the first service gateway and the second service gateway are both connected with the Redis database, and the Redis database stores the working state information of each service gateway and each back-end service instance; in the process of service deployment, firstly, inquiring a Redis database based on a second service gateway to obtain third working state information corresponding to a first service gateway and fourth working state information corresponding to a first back-end service instance; and under the condition that the third working state information indicates that the first service gateway does not perform tasks and the fourth working state information indicates that the first back-end service instance does not perform tasks, deploying the first service gateway and the first back-end service instance to realize deployment processing of the first service gateway and the first back-end service instance.
It may be appreciated that, when the third operating state information indicates that the first service gateway does not perform any task and the fourth operating state information indicates that the first back-end service instance does not perform any task, that is, the third operating state information indicates that the first service gateway does not perform any task, it is suitable for performing a subsequent service deployment operation, and the fourth operating state information indicates that the first back-end service instance does not perform any task, it is suitable for performing a subsequent service deployment operation.
In some embodiments, as shown in fig. 6, the step S600 may include, but is not limited to, steps S610 to S620.
Step S610, after the deployment of the first service gateway and the first back-end service instance is completed, performing verification processing on the first service gateway and the first back-end service instance;
in step S620, in case that the first service gateway and the first backend service instance are both verified successfully, the traffic of the clustered network is redistributed to the first service gateway and the second service gateway.
It should be noted that, after the deployment of the first service gateway and the first back-end service instance is completed, verification processing may also be performed on the first service gateway and the first back-end service instance; and after the first service gateway and the first back-end service instance are successfully verified, redistributing the traffic of the cluster network to the first service gateway and the second service gateway to complete the whole service deployment of the cluster network.
It should be noted that, after the first service gateway and the first back-end service instance are deployed, verification is further required to be performed on the first service gateway and the first back-end service instance so as to detect the service deployment situation; and when the first service gateway and the first back-end service instance are verified successfully, the traffic of the cluster network is redistributed to the first service gateway and the second service gateway, the deployment is completed, the related party calls no abnormality, the seamless update of the service is realized, and better use experience is brought to the use of users.
In some embodiments, as shown in fig. 7, the cluster network further includes a domain name server, and the first service gateway and the second service gateway are both in data connection with the domain name server, and the step S200 may include, but is not limited to, steps S210 to S220.
Step S210, analyzing and processing the service deployment request based on the domain name server to obtain a flow distribution strategy;
step S220, distributing the traffic of the clustered network to the first service gateway based on the traffic distribution policy.
In the process of traffic distribution, firstly, a traffic distribution strategy can be obtained by analyzing and processing a service deployment request based on a domain name server; traffic of the clustered network may then be distributed to the first service gateway based on the traffic distribution policy.
It may be appreciated that the embodiment of the present application only exemplarily illustrates that the traffic in the trunking network is distributed to the first service gateway, and in fact, the traffic may also be distributed to the second service gateway, and then the service deployment is performed on the first service gateway first; the embodiment of the application mainly aims at explaining the distribution of the traffic to one of the nodes in the cluster network so as to facilitate the service deployment of the other nodes, and the situation that the back-end service instance is interrupted due to the service deployment is avoided.
In some embodiments, as shown in fig. 8, the step S320 may include, but is not limited to, step S321.
Step S321, the name of the second back-end service instance is written into the Redis database.
It should be noted that, when the first working state information indicates that the second service gateway does not perform tasks and the second working state information indicates that the second back-end service instance does not perform tasks, the second service gateway and the second back-end service instance are deployed, and names of the second back-end service instance are written into the dis database; when the subsequent other service gateways distribute tasks, only the relevant information in the Redis database is required to be read, so that whether the corresponding back-end service instance can be called or not can be judged, and the task distribution logic is greatly simplified.
In addition, as shown in fig. 9, an embodiment of the present application further provides a service deployment apparatus 10, including:
a first processing module 100, configured to obtain a service deployment request;
a second processing module 200, configured to distribute, according to the service deployment request, traffic of the clustered network to the first service gateway and make the second backend service instance in a maintenance state;
the third processing module 300 is configured to deploy the second service gateway and the second backend service instance if no task is executed by the second service gateway and the second backend service instance;
a fourth processing module 400, configured to distribute, after deployment of both the second service gateway and the second backend service instance is completed, traffic of the clustered network to the second service gateway and make the first backend service instance in a maintenance state;
a fifth processing module 500, configured to deploy the first service gateway and the first back-end service instance when no tasks are performed by the first service gateway and the first back-end service instance;
and a sixth processing module 600, configured to redistribute the traffic of the clustered network to the first service gateway and the second service gateway after the first service gateway and the first backend service instance are deployed.
In one embodiment, a service deployment request is first obtained; distributing the traffic of the cluster network to a first service gateway according to the service deployment request and enabling the second back-end service instance to be in a maintenance state; under the condition that the second service gateway and the second back-end service instance do not have task execution, the second service gateway and the second back-end service instance are deployed; then after the second service gateway and the second back-end service instance are deployed, distributing the traffic of the cluster network to the second service gateway and enabling the first back-end service instance to be in a maintenance state; then, under the condition that the first service gateway and the first back-end service instance do not have task execution, the first service gateway and the first back-end service instance are deployed; and finally, after the first service gateway and the first back-end service instance are deployed, redistributing the traffic of the cluster network to the first service gateway and the second service gateway. Through the technical scheme, service deployment is performed according to the execution condition of the back-end service instance, so that the problem of task loss or service interruption caused by service deployment can be avoided.
The specific implementation manner of the service deployment device is basically the same as the specific embodiment of the service deployment method, and is not repeated here.
In addition, as shown in fig. 10, an embodiment of the present application further provides an electronic device 700, including: memory 710, processor 720, and computer programs stored on memory 710 and executable on processor 720.
The processor 720 and the memory 710 may be connected by a bus or other means.
The non-transitory software programs and instructions required to implement the service deployment methods of the above embodiments are stored in the memory 710, and when executed by the processor 720, the service deployment methods of the above embodiments are performed, for example, the method steps S100 to S600 in fig. 2, the method steps S310 to S320 in fig. 3, the method steps S410 to S420 in fig. 4, the method steps S510 to S520 in fig. 5, the method steps S610 to S620 in fig. 6, the method steps S210 to S220 in fig. 7, and the method step S321 in fig. 8 described above are performed.
The above described apparatus embodiments are merely illustrative, wherein the units illustrated as separate components may or may not be physically separate, i.e. may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
Furthermore, an embodiment of the present application provides a computer-readable storage medium storing computer-executable instructions that are executed by a processor 720 or a controller, for example, by one processor 720 in the above-described device embodiment, which may cause the above-described processor 720 to perform the service deployment method in the above-described embodiment, for example, to perform the above-described method steps S100 to S600 in fig. 2, the method steps S310 to S320 in fig. 3, the method steps S410 to S420 in fig. 4, the method steps S510 to S520 in fig. 5, the method steps S610 to S620 in fig. 6, the method steps S210 to S220 in fig. 7, and the method step S321 in fig. 8.
The embodiments described above may be combined, and modules with the same names may be the same or different between different embodiments.
The foregoing describes certain embodiments of the application, other embodiments being within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. Furthermore, the processes depicted in the accompanying drawings do not necessarily have to be in the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
The embodiments of the present application are described in a progressive manner, and the same and similar parts of the embodiments are all referred to each other, and each embodiment is mainly described in the differences from the other embodiments. In particular, for apparatus, devices, computer readable storage medium embodiments, the description is relatively simple as it is substantially similar to method embodiments, with reference to the section of the method embodiments being relevant.
The apparatus, the device, the computer readable storage medium and the method provided by the embodiments of the present application correspond to each other, and therefore, the apparatus, the device, the non-volatile computer storage medium also have similar beneficial technical effects as those of the corresponding method, and since the beneficial technical effects of the method have been described in detail above, the beneficial technical effects of the corresponding apparatus, device, and computer storage medium are not described here again.
In the 90 s of the 20 th century, improvements to one technology could clearly be distinguished as improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software (improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (e.g., field programmable gate array (Field Programmable Gate Array, FPGA)) is an integrated circuit whose logic function is determined by the programming of the device by a user. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented by using "logic compiler" software, which is similar to the software compiler used in program development and writing, and the original code before the compiling is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but not just one of the hdds, but a plurality of kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), lava, lola, myHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog are currently most commonly used. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers, and embedded microcontrollers, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, atmel AT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in a pure computer readable program code, it is well possible to implement the same functionality by logically programming the method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Such a controller may thus be regarded as a kind of hardware component, and means for performing various functions included therein may also be regarded as structures within the hardware component. Or even means for achieving the various functions may be regarded as either software modules implementing the methods or structures within hardware components.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each unit may be implemented in the same piece or pieces of software and/or hardware when implementing the embodiments of the present application.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the application may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present description is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory, random Access Memory (RAM), and/or nonvolatile memory, such as Read Only Memory (ROM) or Flash memory (Flash RAM), among others, in a computer readable medium. Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable Media, as defined herein, does not include Transitory computer-readable Media (transmission Media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
In the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relation of association objects, and indicates that there may be three kinds of relations, for example, a and/or B, and may indicate that a alone exists, a and B together, and B alone exists. Wherein A, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of the following" and the like means any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c may represent: a, b, c, a and b, a and c, b and c or a and b and c, wherein a, b and c can be single or multiple.
Embodiments of the application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Embodiments of the application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments of the present application are described in a progressive manner, and the same and similar parts of the embodiments are all referred to each other, and each embodiment is mainly described in the differences from the other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.
The foregoing description is only exemplary embodiments of the application and is not intended to limit the application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in the scope of the claims of the present application.
Claims (7)
1. The service deployment method is characterized by being applied to a cluster network, wherein the cluster network comprises a first service gateway, a second service gateway, a first back-end service instance and a second back-end service instance, the first back-end service instance is in data connection with the first service gateway, and the second back-end service instance is in data connection with the second service gateway, and the service deployment method comprises the following steps:
acquiring a service deployment request;
distributing the traffic of the cluster network to the first service gateway according to the service deployment request and enabling the second back-end service instance to be in a maintenance state;
under the condition that the second service gateway and the second back-end service instance do not have task execution, deploying the second service gateway and the second back-end service instance;
after the second service gateway and the second back-end service instance are deployed, distributing traffic of the clustered network to the second service gateway and enabling the first back-end service instance to be in a maintenance state;
under the condition that the first service gateway and the first back-end service instance do not have task execution, the first service gateway and the first back-end service instance are deployed;
After the first service gateway and the first back-end service instance are deployed, redistributing the traffic of the cluster network to the first service gateway and the second service gateway;
the cluster network further includes a remote dictionary service Redis database, the first service gateway and the second service gateway are both in data connection with the Redis database, and the deploying the second service gateway and the second back-end service instance under the condition that the second service gateway and the second back-end service instance do not have task execution includes:
inquiring the Redis database based on the first service gateway to obtain first working state information corresponding to the second service gateway and second working state information corresponding to the second back-end service instance;
the second service gateway and the second back-end service instance are deployed under the condition that the first working state information indicates that the second service gateway does not execute tasks and the second working state information indicates that the second back-end service instance does not execute tasks;
the deploying the first service gateway and the first back-end service instance under the condition that the first service gateway and the first back-end service instance do not have tasks to execute includes:
Inquiring the Redis database based on the second service gateway to obtain third working state information corresponding to the first service gateway and fourth working state information corresponding to the first back-end service instance;
deploying the first service gateway and the first back-end service instance under the condition that the third working state information indicates that the first service gateway does not execute tasks and the fourth working state information indicates that the first back-end service instance does not execute tasks;
the deploying the second service gateway and the second back-end service instance after the first working state information indicates that the second service gateway has no task execution and the second working state information indicates that the second back-end service instance has no task execution further includes:
and writing the name of the second back-end service instance into the Redis database.
2. The service deployment method according to claim 1, wherein said distributing traffic of the clustered network to the second service gateway and placing the first back-end service instance in a maintenance state after deployment of both the second service gateway and the second back-end service instance is completed comprises:
After the second service gateway and the second back-end service instance are deployed, verifying the second service gateway and the second back-end service instance;
and distributing the traffic of the cluster network to the second service gateway and enabling the first back-end service instance to be in a maintenance state under the condition that the second service gateway and the second back-end service instance are successfully verified.
3. The service deployment method of claim 1, wherein redistributing traffic of the clustered network to the first service gateway and the second service gateway after deployment of both the first service gateway and the first backend service instance is completed, comprises:
after the first service gateway and the first back-end service instance are deployed, verifying the first service gateway and the first back-end service instance;
and under the condition that the first service gateway and the first back-end service instance are successfully verified, redistributing the traffic of the cluster network to the first service gateway and the second service gateway.
4. The service deployment method of claim 1, wherein the clustered network further comprises a domain name server, wherein the first service gateway and the second service gateway are each in data connection with the domain name server, wherein the distributing traffic of the clustered network to the first service gateway according to the service deployment request comprises:
Analyzing and processing the service deployment request based on the domain name server to obtain a flow distribution strategy;
and distributing the traffic of the cluster network to the first service gateway based on the traffic distribution policy.
5. A service deployment apparatus, applied to a clustered network, the clustered network including a first service gateway, a second service gateway, a first back-end service instance, and a second back-end service instance, the first back-end service instance being in data connection with the first service gateway, the second back-end service instance being in data connection with the second service gateway, the apparatus comprising:
the first processing module is used for acquiring a service deployment request;
the second processing module is used for distributing the traffic of the cluster network to the first service gateway according to the service deployment request and enabling the second back-end service instance to be in a maintenance state;
the third processing module is used for deploying the second service gateway and the second back-end service instance under the condition that the second service gateway and the second back-end service instance do not have task execution;
a fourth processing module, configured to distribute, after deployment of both the second service gateway and the second backend service instance is completed, traffic of the clustered network to the second service gateway and cause the first backend service instance to be in a maintenance state;
A fifth processing module, configured to deploy the first service gateway and the first backend service instance when no task is executed by the first service gateway and the first backend service instance;
a sixth processing module, configured to redistribute, after deployment of both the first service gateway and the first backend service instance is completed, traffic of the clustered network to the first service gateway and the second service gateway;
the cluster network further includes a remote dictionary service Redis database, the first service gateway and the second service gateway are both in data connection with the Redis database, and the deploying the second service gateway and the second back-end service instance under the condition that the second service gateway and the second back-end service instance do not have task execution includes:
inquiring the Redis database based on the first service gateway to obtain first working state information corresponding to the second service gateway and second working state information corresponding to the second back-end service instance;
the second service gateway and the second back-end service instance are deployed under the condition that the first working state information indicates that the second service gateway does not execute tasks and the second working state information indicates that the second back-end service instance does not execute tasks;
The deploying the first service gateway and the first back-end service instance under the condition that the first service gateway and the first back-end service instance do not have tasks to execute includes:
inquiring the Redis database based on the second service gateway to obtain third working state information corresponding to the first service gateway and fourth working state information corresponding to the first back-end service instance;
deploying the first service gateway and the first back-end service instance under the condition that the third working state information indicates that the first service gateway does not execute tasks and the fourth working state information indicates that the first back-end service instance does not execute tasks;
the deploying the second service gateway and the second back-end service instance after the first working state information indicates that the second service gateway has no task execution and the second working state information indicates that the second back-end service instance has no task execution further includes:
and writing the name of the second back-end service instance into the Redis database.
6. An electronic device, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the service deployment method according to any of claims 1 to 4 when executing the computer program.
7. A computer-readable storage medium storing computer-executable instructions for performing the service deployment method of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210860784.XA CN115225638B (en) | 2022-07-21 | 2022-07-21 | Service deployment method, device, electronic equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210860784.XA CN115225638B (en) | 2022-07-21 | 2022-07-21 | Service deployment method, device, electronic equipment and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115225638A CN115225638A (en) | 2022-10-21 |
| CN115225638B true CN115225638B (en) | 2023-09-15 |
Family
ID=83613831
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210860784.XA Active CN115225638B (en) | 2022-07-21 | 2022-07-21 | Service deployment method, device, electronic equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115225638B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110474907A (en) * | 2019-08-16 | 2019-11-19 | 北京明朝万达科技股份有限公司 | Service bus system and system is served by based on service bus |
| CN110990025A (en) * | 2019-12-06 | 2020-04-10 | 无锡华云数据技术服务有限公司 | Instance deployment method and system |
| CN112597013A (en) * | 2020-12-16 | 2021-04-02 | 北京三快在线科技有限公司 | Online development and debugging method and device |
| CN113268351A (en) * | 2021-06-07 | 2021-08-17 | 北京金山云网络技术有限公司 | Load balancing method and device for gateway service |
| CN113741924A (en) * | 2020-05-28 | 2021-12-03 | 中国移动通信集团浙江有限公司 | Application deployment method, system and server |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9775008B2 (en) * | 2015-01-14 | 2017-09-26 | Kodiak Networks, Inc. | System and method for elastic scaling in a push to talk (PTT) platform using user affinity groups |
-
2022
- 2022-07-21 CN CN202210860784.XA patent/CN115225638B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110474907A (en) * | 2019-08-16 | 2019-11-19 | 北京明朝万达科技股份有限公司 | Service bus system and system is served by based on service bus |
| CN110990025A (en) * | 2019-12-06 | 2020-04-10 | 无锡华云数据技术服务有限公司 | Instance deployment method and system |
| CN113741924A (en) * | 2020-05-28 | 2021-12-03 | 中国移动通信集团浙江有限公司 | Application deployment method, system and server |
| CN112597013A (en) * | 2020-12-16 | 2021-04-02 | 北京三快在线科技有限公司 | Online development and debugging method and device |
| CN113268351A (en) * | 2021-06-07 | 2021-08-17 | 北京金山云网络技术有限公司 | Load balancing method and device for gateway service |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115225638A (en) | 2022-10-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110134668B (en) | Data migration method, device and equipment applied to blockchain | |
| CN111400681B (en) | Data authority processing method, device and equipment | |
| CN114327759B (en) | Method and device for processing block chain data | |
| CN112231384B (en) | Distributed application localization transformation method and equipment adapting to multiple data sources | |
| CN112597013A (en) | Online development and debugging method and device | |
| CN110430255A (en) | The processing method of service request, system and electronic equipment in distributed type assemblies | |
| CN116483859A (en) | Data query method and device | |
| CN116305298A (en) | Method and device for managing computing power resources, storage medium and electronic equipment | |
| CN110046052B (en) | Service calling method and device | |
| CN117971782A (en) | Mirror image management method and server | |
| CN115225638B (en) | Service deployment method, device, electronic equipment and computer readable storage medium | |
| CN110245166B (en) | Data checking method and device | |
| CN110874322B (en) | Test method and test server for application program | |
| CN111796864A (en) | Data verification method and device | |
| CN116382713A (en) | Method, system, device and storage medium for constructing application mirror image | |
| CN111339117B (en) | Data processing method, device and equipment | |
| CN105338025B (en) | Invocation component method, system, client and concentration assembly method and server | |
| CN113867776A (en) | Method and device for publishing middle station application, electronic equipment and storage medium | |
| CN113761400A (en) | Access request forwarding method, device and equipment | |
| CN117041980B (en) | Network element management method and device, storage medium and electronic equipment | |
| CN117519733B (en) | Project deployment method and device, storage medium and electronic equipment | |
| CN110413935B (en) | Data information processing method, device and system | |
| CN114546524B (en) | Application authority processing method and device | |
| CN110321250B (en) | Disaster recovery method and device for application | |
| CN117914721A (en) | Java-based call substitute service system construction method and device |
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 |