CN112394951B - Application deployment method and server cluster - Google Patents
Application deployment method and server cluster Download PDFInfo
- Publication number
- CN112394951B CN112394951B CN202011267872.6A CN202011267872A CN112394951B CN 112394951 B CN112394951 B CN 112394951B CN 202011267872 A CN202011267872 A CN 202011267872A CN 112394951 B CN112394951 B CN 112394951B
- Authority
- CN
- China
- Prior art keywords
- server
- list
- application
- target
- deployment
- 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
- 238000000034 method Methods 0.000 title claims abstract description 58
- 238000013515 script Methods 0.000 claims description 26
- 230000001360 synchronised effect Effects 0.000 claims description 5
- 230000008569 process Effects 0.000 description 11
- 238000010586 diagram Methods 0.000 description 8
- 238000004590 computer program Methods 0.000 description 7
- 230000004992 fission Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 230000000977 initiatory effect Effects 0.000 description 5
- 238000009434 installation Methods 0.000 description 5
- 230000005856 abnormality Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
Abstract
The application provides an application deployment method and a server cluster, which can be used in the financial field or other fields, and the method comprises the following steps: the target server receives a version package of the target application; the target server executes a deployment step, wherein the deployment step comprises: completing the deployment of the target application according to the version package; deleting the record of the target server in the preset server list; if the preset server list is not empty currently, the version package is sent to the next server; and taking the next server as a target server, and returning to execute the deployment step. The application can support concurrent deployment of a large number of servers, reduce consumption of the servers and network resources, and further improve reliability of application deployment.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to an application deployment method and a server cluster.
Background
As the application of distributed processing is more and more widespread, linux/Unix servers are more and larger in scale, and when applications are installed and deployed, batch executed and batch synchronized, versions often need to be deployed on a large number of servers. If the deployment is carried out in a serial mode, the time consumption is longer; if the background parallel mode is adopted, a large number of processes are generated, so that great pressure is caused on an initiating server, a large number of version packages are transmitted concurrently, and the network resource occupation and consumption are great.
Disclosure of Invention
Aiming at the problems in the prior art, the application provides an application deployment method and a server cluster, which can support concurrent deployment of a large number of servers, reduce consumption of servers and network resources, and further improve reliability of application deployment.
In order to solve the technical problems, the application provides the following technical scheme:
in a first aspect, the present application provides an application deployment method, including:
the target server receives a version package of the target application;
the target server executes a deployment step, wherein the deployment step comprises: completing the deployment of the target application according to the version package; deleting the record of the target server in the preset server list; if the preset server list is not empty currently, the version package is sent to the next server;
and taking the next server as a target server, and returning to execute the deployment step.
Further, if the preset server list is not currently empty, the sending the version package to the next server includes:
if the preset server list currently comprises a plurality of records, splitting the preset server list into a plurality of sub-lists;
selecting one server from the servers corresponding to the sub-lists as a next server;
and sending the version package and the sub-list to the next server.
Further, the step of returning the next server as the target server to execute the deployment step includes:
and taking the sub-list as the preset server list, taking the next server as a target server, and returning to execute the deployment step.
Further, after deleting the record of the target server in the preset server list, the method further includes:
if the preset server list is currently empty, the target server ends the current deployment step.
Further, if the preset server list is not currently empty, the sending the version package to the next server includes:
if the preset server list only has a unique record currently, the server corresponding to the record is used as the next server, and the version package is sent to the next server.
Further, the record in the preset server list includes: internet protocol address, port, user and password information of the server; correspondingly, if the preset server list is not empty currently, the version package is sent to the next server, which includes:
and if the preset server list is not empty currently, sending the version package to the next server according to the Internet protocol address, the port, the user and the password information of the next server.
Further, the sending the version package and the sub-list to the next server includes:
obtaining a plurality of application deployment files according to the version package and each sub-list, wherein each application deployment file comprises: the version package and the unique sub-list; and the sub-lists in each of the application deployment files are different;
and compressing each application deployment file and then sending the compressed application deployment file to the corresponding next server.
Further, the target server receives a version package of the target application, and the method further includes:
the target server receives a synchronization script;
correspondingly, the target server executes a deployment step, including:
and the target server executes the deployment step by applying the synchronous script.
Further, the deleting the record of the target server in the preset server list includes:
and logically deleting or physically deleting the record of the target server in the preset server list.
In a second aspect, the present application provides a server cluster, comprising:
and the application deployment among the servers adopts the application deployment method.
According to the technical scheme, the application provides an application deployment method and a server cluster. Wherein the method comprises the following steps: the target server receives a version package of the target application; the target server executes a deployment step, wherein the deployment step comprises: completing the deployment of the target application according to the version package; deleting the record of the target server in the preset server list; if the preset server list is not empty currently, the version package is sent to the next server; the next server is used as a target server, and the deployment step is executed in a return mode, so that consumption of the server and network resources can be reduced while a large number of servers are supported for concurrent deployment, and further reliability of application deployment can be improved; specifically, compared with the traditional parallel deployment mode, the concurrent processing in the application deployment method provided by the application is distributed, the server list is split only on each target server, so that the consumption is very small, a large number of processes are not generated in a concentrated way, and the problem that the server resources are consumed in a large amount to cause abnormality or downtime can be avoided; the network resource consumption can be reduced, and application deployment, batch execution or batch synchronization can be realized; namely, the method can support concurrent deployment of a large number of servers and greatly reduce the consumption of the occupied resources of the initiating server and the network.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a first flow of an application deployment method according to an embodiment of the present application;
FIG. 2 is a flow chart of an application deployment method in a further embodiment of the present application;
FIG. 3 is a flowchart illustrating steps 201 to 203 of an application deployment method according to an embodiment of the present application;
FIG. 4 is a flow chart of an application deployment method in an application example of the present application;
fig. 5 is a functional block diagram of an example application deployment method of the present application.
Detailed Description
In order to make the technical solutions in the present specification better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some embodiments of the present application, but not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
It should be noted that, the application deployment method and the server cluster disclosed by the application can be used in the financial technical field, and also can be used in any field except the financial technical field, and the application field of the application deployment method and the server cluster disclosed by the application is not limited.
The following examples are presented in detail.
In order to support concurrent deployment of a large number of servers and reduce consumption of server and network resources and further improve reliability of application deployment, the embodiment provides an application deployment method, as shown in fig. 1, which specifically includes the following contents:
step 101: the target server receives the version package of the target application.
Specifically, the target server may be a server corresponding to any record in the preset server list; the version package of the target application sent by an independent server or client can be received; the version package can comprise service scripts required by deploying the target application, and the deployment of the target application is realized by executing the service scripts; the target server may be a Linux/Unix server.
Step 102: the target server performs a deployment step, wherein, referring to fig. 2, the deployment step includes:
step 1021: and completing the deployment of the target application according to the version package.
Step 1022: and deleting the record of the target server in the preset server list.
The preset server list may include: records corresponding to a plurality of servers, each record comprising: information such as internet protocol address, port, user and password of the server; specific data in the preset server list can be set according to actual conditions, and the comparison of the application is not limited. The preset server list can be a server list sent by an independent server or a client, or can be a sub-list sent by a last target server.
Step 1023: and if the preset server list is not empty currently, sending the version package to the next server.
Specifically, the record of the target server in the preset server list may be deleted logically or physically; further, if the network resource of the target server is smaller than the preset network resource amount, the deleted server list can be split into two sub-lists, so that the minimum network resource consumption is obtained, and the reliability of application deployment is improved; if the network resource of the target server is greater than or equal to the preset network resource amount, splitting the network resource into more than two sub-lists so as to improve the efficiency of application deployment on the basis of ensuring the reliability of the application deployment, wherein the network resource can be a network bandwidth; the preset network resource amount may be a preset network bandwidth, and may be set according to actual needs.
Step 103: and taking the next server as a target server, and returning to execute the deployment step.
As can be seen from the above description, the application deployment method provided by the present embodiment is a split application deployment method, in which an application version is deployed on each target server in a manner of fissioning a server list, so that the occupation consumption of an initiating server and network resources can be greatly reduced while a large number of concurrent deployments of servers are supported, and the purposes of high efficiency, stability and small network resource consumption of application deployment are achieved; batch execution and synchronous execution of application deployment in multiple servers can be realized.
To further reduce the consumption of the originating server and network resources, and to ensure the reliability of the application deployment, see fig. 3, in one embodiment of the present application, step 1023 includes:
step 201: if the preset server list currently comprises a plurality of records, splitting the preset server list into a plurality of sub-lists.
Step 202: and selecting one server from the servers corresponding to the sub-lists as the next server.
Step 203: and sending the version package and the sub-list to the next server.
Specifically, each sub-list may be respectively used as the preset server list, the next server corresponding to each sub-list is respectively used as a target server, and each target server simultaneously returns to execute the deployment step, so as to realize distributed concurrent processing in the application deployment process, and reduce resource consumption of concurrent processing.
It can be understood that if the deleted server list includes a plurality of records, splitting the preset server list into a plurality of sub-lists, where each sub-list includes at least one record; if two sub-lists exist, one of the servers corresponding to one of the sub-lists can be selected as the next server, and one of the servers corresponding to the other sub-list can be selected as the next server.
To further reduce the consumption of the originating server and network resources, and ensure the reliability of the application deployment, in one embodiment of the present application, step 1024 includes:
step 301: and taking the sub-list as the preset server list, taking the next server as a target server, and returning to execute the deployment step.
In order to further reduce the resource consumption in the application deployment process and improve the efficiency and reliability of application deployment, referring to fig. 2, in one embodiment of the present application, after step 1022, the method further includes:
step 401: if the preset server list is currently empty, the target server ends the current deployment step.
It will be appreciated that if the deleted server list is empty, then there is no next server.
In order to further reduce the resource consumption in the application deployment process and improve the efficiency and reliability of application deployment, in one embodiment of the present application, step 1023 includes:
step 501: if the preset server list only has a unique record currently, the server corresponding to the record is used as the next server, and the version package is sent to the next server.
In order to improve security in the application deployment process, in one embodiment of the present application, the record in the preset server list includes: internet protocol address, port, user and password information of the server; correspondingly, step 1023 includes:
step 601: and if the preset server list is not empty currently, sending the version package to the next server according to the Internet protocol address, the port, the user and the password information of the next server.
In order to further reduce the resource consumption in the application deployment process and improve the data transmission efficiency, in one embodiment of the present application, step 203 includes:
step 701: obtaining a plurality of application deployment files according to the version package and each sub-list, wherein each application deployment file comprises: the version package and the unique sub-list; and the sub-lists in each of the application deployment files are different;
step 702: and compressing each application deployment file and then sending the compressed application deployment file to the corresponding next server.
It can be understood that if one server is selected from the servers corresponding to the sub-list as the next server, the next server is used as the next server corresponding to the application deployment file where the sub-list is located.
To further illustrate the present solution, in one embodiment of the present application, step 101 further includes:
step 601: the target server receives a synchronization script; correspondingly, step 102 includes:
step 602: and the target server executes the deployment step by applying the synchronous script.
Specifically, in the deploying step, the synchronization script may be transmitted to the next server while the version package is transmitted to the next server.
To further illustrate the present solution, the present application provides a server cluster, including:
and the application deployment among the servers adopts the application deployment method.
Specifically, the server cluster is configured to implement the application deployment method, where each server may be in communication connection with each other, and the servers are in one-to-one correspondence with records in the preset server list.
In order to support concurrent deployment of a large number of servers and reduce consumption of server and network resources and further improve reliability of application deployment, the application provides an application example of an application deployment method, referring to fig. 4, in the application example, the method comprises:
step S11: the target server receives the version package, the synchronization script and the server list; i.e. the version package, synchronization script and server list are transferred to a target server.
The target server can be used for receiving and storing version packages, synchronization scripts and sub-list lists, and realizing the functions of synchronization script execution, server list fission, service script execution, installation and deployment, processed server IP deletion (or processed) and the like; version packages, synchronization scripts, and server lists may be transmitted over a network.
Step S12: executing a synchronization script; i.e. start the synchronization script and direct the execution of the subsequent steps.
Step S13: executing the service script, and carrying out version installation and deployment; and executing the service script in the version package on the current target server to perform version installation and deployment.
Step S14: deleting the IP of the target server (or setting the IP as processed) in the server list; the record of the target server may be deleted.
Step S15: judging whether the server list is empty or not; if yes, the processing of the current target server is ended, otherwise, step S16 is executed.
Step S16: and reading information such as IP, port, user, password and the like in the server list.
Step S17: splitting the server list to form a plurality of sub-lists.
Step S18: the sub-list and synchronization script are added to the version of the compressed package file.
Step S19: transmitting the compressed package file to a certain target server in the sub-list; the execution of the processing continues from step S12.
For further explanation of the present solution, referring to fig. 5, in an example of the present application, the list is split in half, and the application deployment method specifically includes:
in the server cluster, firstly, a version package, a synchronization script and a server list are transmitted to a server 011, the synchronization script is started, a service script is executed to carry out version installation and deployment, and the IP of the server 011 is deleted (or set as processed) in the server list; then reading information such as IP, port, user and password of the server list; then splitting the server list in half to form a sub-list 1 and a sub-list 2; finally, the "sub-list 1" and the synchronization script are added into the version of the compressed package file, and transmitted to one of the servers 021 of the "sub-list 1", and then the "sub-list 2" and the synchronization script are added into the version of the compressed package file, and transmitted to one of the servers 022 of the "sub-list 2".
The servers 021 and 022 execute the same actions and steps as the server 011, namely after receiving the version package, the synchronization script and the sub-list transmitted by the server 011, split the sub-list and transmit the split sub-list to the servers 031 and 032 and the servers 033 and 034 respectively.
Servers 031, 032, 033, 034 split the list as well and cause the remaining servers to split.
Finally, when server X 1 、X 2 、……X y When only one record is received in the sub-list, only the version installation part is carried outAnd (5) deploying, namely not splitting the list, and ending the fission.
As can be seen from the above description, the application deployment method and the server cluster provided by the application can solve the problem that the initiation server is abnormal or down due to a large number of processes generated by common serial processing with long time and parallel processing, and can greatly reduce the occupation consumption of the initiation server and network resources while supporting the concurrent deployment of a large number of servers, and the application has the following specific advantages:
1. compared with the traditional parallel deployment mode, the concurrent processing in the application deployment process is distributed, the IP list is split only on each target server, so that the consumption is extremely low, a large number of processes are not generated in a centralized manner, and the server resources are not consumed in a large amount to cause abnormality or downtime.
2. The application deployment method provided by the application has the advantages that the maximum network resource consumption is about the original (C-1)/C, wherein C represents the fission speed, such as half fission, each father node is split into 2 child nodes, C=2, and the maximum network resource consumption is only about 1/2 of the original, so that the method is optimal, and is very suitable for application deployment, batch execution or batch synchronization under the condition of limited network resources; other faster fission speeds, C >2, network resource consumption between about 50% and 100% of the original network resource consumption, and are suitable for application deployment, batch execution or batch synchronization under the condition of sufficient network resources.
The embodiments of the method 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 mainly describes differences from other embodiments. For relevance, see the description of the method embodiments.
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, 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, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application 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.
The principles and embodiments of the present application have been described in detail with reference to specific examples, which are provided to facilitate understanding of the method and core ideas of the present application; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.
Claims (9)
1. An application deployment method, comprising:
the target server receives a version package of the target application;
the target server executes a deployment step, wherein the deployment step comprises: completing the deployment of the target application according to the version package; deleting the record of the target server in the preset server list; if the preset server list is not empty currently, the version package is sent to the next server;
the next server is used as a target server, and the deployment step is executed in a returning mode;
and if the preset server list is not currently empty, sending the version package to a next server, including:
if the preset server list currently comprises a plurality of records, splitting the preset server list into a plurality of sub-lists;
selecting one server from the servers corresponding to the sub-lists as a next server;
and sending the version package and the sub-list to the next server.
2. The application deployment method according to claim 1, wherein said returning the next server as the target server to execute the deploying step includes:
and taking the sub-list as the preset server list, taking the next server as a target server, and returning to execute the deployment step.
3. The application deployment method according to claim 1, further comprising, after the deleting the record of the target server in the preset server list:
if the preset server list is currently empty, the target server ends the current deployment step.
4. The application deployment method according to claim 1, wherein if the preset server list is not currently empty, sending the version package to a next server includes:
if the preset server list only has a unique record currently, the server corresponding to the record is used as the next server, and the version package is sent to the next server.
5. The application deployment method of claim 1, wherein the record in the preset server list comprises: internet protocol address, port, user and password information of the server; correspondingly, if the preset server list is not empty currently, the version package is sent to the next server, which includes:
and if the preset server list is not empty currently, sending the version package to the next server according to the Internet protocol address, the port, the user and the password information of the next server.
6. The application deployment method of claim 1 wherein said sending the version package and sub-list to the next server comprises:
obtaining a plurality of application deployment files according to the version package and each sub-list, wherein each application deployment file comprises: the version package and the unique sub-list; and the sub-lists in each of the application deployment files are different;
and compressing each application deployment file and then sending the compressed application deployment file to the corresponding next server.
7. The application deployment method of claim 1 wherein the target server receives a version package of the target application, further comprising:
the target server receives a synchronization script;
correspondingly, the target server executes a deployment step, including:
and the target server executes the deployment step by applying the synchronous script.
8. The application deployment method according to claim 1, wherein the deleting the record of the target server in the preset server list includes:
and logically deleting or physically deleting the record of the target server in the preset server list.
9. A server cluster, comprising:
a plurality of servers, wherein application deployment among the servers adopts the application deployment method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011267872.6A CN112394951B (en) | 2020-11-13 | 2020-11-13 | Application deployment method and server cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011267872.6A CN112394951B (en) | 2020-11-13 | 2020-11-13 | Application deployment method and server cluster |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112394951A CN112394951A (en) | 2021-02-23 |
| CN112394951B true CN112394951B (en) | 2023-11-17 |
Family
ID=74600185
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011267872.6A Active CN112394951B (en) | 2020-11-13 | 2020-11-13 | Application deployment method and server cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112394951B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108228438A (en) * | 2017-12-29 | 2018-06-29 | 广州品唯软件有限公司 | The performance test methods and device of a kind of mobile terminal |
| CN109753301A (en) * | 2018-12-06 | 2019-05-14 | 东软集团股份有限公司 | Application system dispositions method, device, storage medium and electronic equipment |
| CN110489090A (en) * | 2019-08-19 | 2019-11-22 | 中国工商银行股份有限公司 | A kind of applied software development method and system based on application model |
| CN110532189A (en) * | 2019-07-18 | 2019-12-03 | 中国人民财产保险股份有限公司 | A kind of continuous integration system, method and device |
-
2020
- 2020-11-13 CN CN202011267872.6A patent/CN112394951B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108228438A (en) * | 2017-12-29 | 2018-06-29 | 广州品唯软件有限公司 | The performance test methods and device of a kind of mobile terminal |
| CN109753301A (en) * | 2018-12-06 | 2019-05-14 | 东软集团股份有限公司 | Application system dispositions method, device, storage medium and electronic equipment |
| CN110532189A (en) * | 2019-07-18 | 2019-12-03 | 中国人民财产保险股份有限公司 | A kind of continuous integration system, method and device |
| CN110489090A (en) * | 2019-08-19 | 2019-11-22 | 中国工商银行股份有限公司 | A kind of applied software development method and system based on application model |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112394951A (en) | 2021-02-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107465767B (en) | Data synchronization method and system | |
| US11940965B2 (en) | Data migration method and apparatus | |
| CN111641515B (en) | VNF life cycle management method and device | |
| CN110247984B (en) | Service processing method, device and storage medium | |
| CN109375933B (en) | Method and equipment for upgrading client | |
| TW201246103A (en) | Category information transmission method, system and apparatus | |
| EP3767895B1 (en) | Method and system for audio and video interaction between plurality of groups | |
| CN110971702A (en) | Service calling method and device, computer equipment and storage medium | |
| CN102323888A (en) | A kind of diskless computer starts accelerated method | |
| CN108111630B (en) | Zookeeper cluster system and connection method and system thereof | |
| CN114401261A (en) | File downloading method and device | |
| CN112394951B (en) | Application deployment method and server cluster | |
| CN111147585B (en) | Equipment upgrading method, device, storage medium and system | |
| CN110018875B (en) | Desktop synchronization implementation method based on IDV | |
| CN112328693A (en) | Block synchronization method, device and storage medium | |
| CN112019614A (en) | Method, system and processor for communication and communication synchronization between two systems | |
| CN110912979A (en) | Method for solving multi-server resource synchronization conflict | |
| CN110798358A (en) | Distributed service identification method and device, computer readable medium and electronic equipment | |
| CN111741102B (en) | Upgrading method and device for distributed micro-service application | |
| CN104468767A (en) | Method and system for detecting cloud storage data collision | |
| CN111431951B (en) | Data processing method, node equipment, system and storage medium | |
| US10419368B1 (en) | Dynamic scaling of computing message architecture | |
| CN115827174B (en) | Task processing method and device based on multiple instances | |
| CN111797062B (en) | Data processing method, device and distributed database system | |
| US20230385533A1 (en) | Method and system for providing edit service of document |
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 |