WO2023240933A1

WO2023240933A1 - Distributed application deployment method and apparatus based on blockchain

Info

Publication number: WO2023240933A1
Application number: PCT/CN2022/135258
Authority: WO
Inventors: 庞洋; 王志伟; 孙兵兵
Original assignee: 蚂蚁区块链科技(上海)有限公司
Priority date: 2022-06-14
Filing date: 2022-11-30
Publication date: 2023-12-21
Also published as: CN115098114A

Abstract

Provided in the embodiments of the present description are a distributed application deployment method and apparatus based on a blockchain. The method comprises: a first computing node acquiring, from a blockchain, first application information of a target application, wherein the first application information comprises connection information of a second computing node, and the first application information is uploaded to the blockchain by means of the second computing node; the first computing node determining, on the basis of the first application information, whether it is necessary to deploy the target application; and if it is necessary to deploy the target application, the first computing node acquiring, from the second computing node and according to the connection information of the second computing node, a first application package of the target application, and deploying the target application. In this way, after a second computing node releases a target application, a first computing node can automatically and dynamically deploy the target application, such that the deployment efficiency, security and stability of the target application are improved.

Description

A distributed application deployment method and device based on blockchain

This application requests the priority of the Chinese patent application submitted to the State Intellectual Property Office of China on June 14, 2022, with application number 2022106686230 and the application name "A blockchain-based distributed application deployment method and device", which The entire contents are incorporated herein by reference.

Technical field

The embodiments of this specification belong to the field of blockchain technology, and particularly relate to a distributed application deployment method and device based on blockchain.

Background technique

Blockchain is a new application model of computer technology such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. In the blockchain system, data blocks are combined into a chain data structure in a sequential manner according to time sequence, and cryptography is used to ensure that the data cannot be tampered with or forged. Due to the characteristics of blockchain, such as decentralization, non-tamperable information, and autonomy, blockchain has also received more and more attention and applications. Blockchain can generally be divided into three categories: public blockchain, private blockchain and consortium blockchain according to different application scenarios and user needs.

Contents of the invention

The embodiments of this specification are intended to provide a blockchain-based distributed application deployment method, device, computer-readable storage medium and computing device, which improves the deployment efficiency of distributed applications.

In order to achieve the above purpose, the first aspect of this specification provides a distributed application deployment method based on the blockchain. The method is executed by the first computing node and includes: obtaining the first application information of the target application from the blockchain, The first application information includes connection information of a second computing node, and the first application information is uploaded to the blockchain through the second computing node; based on the first application information, it is determined whether it is necessary to deploy the Target application; if the target application needs to be deployed, obtain the first installation package of the target application from the second computing node according to the connection information, and deploy the target application based on the first installation package.

A second aspect of this specification provides a blockchain-based distributed application deployment method. The method is executed by a second computing node and includes: obtaining a release request for a target application, where the release request includes the target application. First application information and a first installation package, the first application information including connection information of the second computing node; uploading the first application information to the second computing node through the second blockchain node in the blockchain In the blockchain, the first installation package is stored, wherein the second blockchain node is a node in the blockchain that is connected to the second computing node.

A second aspect of this specification provides a blockchain-based distributed application deployment method. The method is executed by a first blockchain node and includes: receiving a first transaction for calling a smart contract, the first transaction being performed by The second computing node connected to the second blockchain node sends it to the blockchain, the first transaction includes the first application information of the target application, and the first application information includes the second computing node’s Connection information, the first installation package of the target application is stored in the second computing node; according to the first transaction, the first application information is stored in the contract state of the smart contract; from the first The computing node receives a second transaction for calling a smart contract, the second transaction is used to query application information; and sends the first application information in the contract state to the first calculation according to the second transaction. node so that the first computing node obtains the first installation package of the target application from the second computing node according to the connection information.

The fourth aspect of this specification provides a blockchain-based distributed application deployment device, which is deployed on a first computing node. The device includes: an acquisition module configured to acquire the first application information of the target application from the blockchain, The first application information includes the node identification of the second computing node, and the first application information is uploaded to the blockchain through the second computing node; the determination module is configured to determine, based on the first application information, Whether the target application needs to be deployed; the acquisition module is further configured to obtain the first installation package of the target application from the second computing node when the judgment module determines that the target application needs to be deployed; A processing module configured to deploy the target application based on the first installation package when the acquisition module obtains the first installation package.

A fifth aspect of this specification provides a blockchain-based distributed application deployment device deployed on a second computing node. The device includes: an acquisition module configured to obtain a release request for a target application, where the release request includes The first application information and the first installation package of the target application; a processing module configured to upload the first application information to the blockchain through the second blockchain node in the blockchain, and store In the first installation package, the second blockchain node is a node in the blockchain that is connected to the second computing node.

A sixth aspect of this specification provides a blockchain-based distributed application deployment device, deployed at a first blockchain node, including: an acquisition module configured to receive a first transaction for calling a smart contract, the first The transaction is sent to the blockchain by a second computing node connected to the second blockchain node. The first transaction includes first application information of the target application, and the first application information includes the second computing node. The connection information of the node, the first installation package of the target application is stored in the second computing node; the processing module is configured to store the first application information in the smart contract according to the first transaction. In the contract state; the acquisition module is also configured to receive a second transaction for calling the smart contract from the first computing node, and the second transaction is used to query application information; the processing module is also configured to according to the The second transaction sends the first application information in the contract state to the first computing node so that the first computing node obtains the target application from the second computing node according to the connection information. The first installation package.

A seventh aspect of this specification provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed in a computing device, the computing device executes the above-mentioned first aspect, second aspect or third aspect. method.

An eighth aspect of this specification provides a computing device, including a memory and a processor. A computer program is stored in the memory. When the processor executes the computer program, the first aspect, the second aspect or the third aspect are implemented. described method.

Through the methods and devices provided in one or more embodiments of this specification, the first computing node can obtain the application information of the published target application from the blockchain, and through the application information, it can be compared with the information stored in the target application. The second computing node communicates with the first installation package to obtain the first installation package and deploy the target application, thereby realizing automatic and dynamic deployment of the target application and improving the deployment efficiency, security and stability of the target application.

Description of the drawings

In order to explain the technical solutions of the embodiments of this specification more clearly, the drawings needed to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some of the embodiments recorded in this specification. , for those of ordinary skill in the art, other drawings can also be obtained based on these drawings without exerting creative labor.

Figure 1 is a system architecture diagram of the blockchain system in an embodiment of this specification;

Figure 2 is a schematic flow chart of a blockchain-based distributed application deployment method in an embodiment of this specification;

Figure 3 is a schematic diagram of the steps for a first computing node to obtain a first installation package from a second computing node in an embodiment of this specification;

Figure 4 is a schematic structural diagram of a blockchain-based distributed application deployment device provided in the embodiment of this specification;

Figure 5 is a schematic structural diagram of another blockchain-based distributed application deployment device provided in the embodiment of this specification;

Figure 6 is a schematic structural diagram of yet another blockchain-based distributed application deployment device provided in the embodiment of this specification.

Detailed ways

In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of this specification. Obviously, the described The embodiments are only some of the embodiments of this specification, but not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts should fall within the scope of protection of this specification.

Generally, when deploying DAPP (distributed application) in some specific scenarios (such as anti-fraud scenarios, etc.), because DAPP developers often belong to different institutions/companies, and DAPPs are often deployed in various institutions /In the company’s intranet environment, developers cannot access the institutions/companies that need to deploy DAPP in the external network environment. Therefore, when developers deploy DAPP, they often need to go to various institutions/companies for manual deployment. The number of deployments is: N*M*P*O; N is the number of distributed application developers, and M is each The number of DAPPs developed by developers, P is the number of nodes that need to be deployed, and O is the number of DAPP version iterations. The scale of developer deployment will increase exponentially as the number of nodes to be deployed and/or the number of DAPPs increases, and deployment efficiency and speed will also become a major obstacle to business development.

In addition, because developers cannot evaluate the environmental diversity of the edge computing servers (hereinafter referred to as "computing nodes") where DAPP needs to be deployed, this leads to developers being prone to incompatibility issues when deploying DAPP. As for the basic capabilities that DAPP relies on (mysql, redis, etc.), when DAPP is deployed on different computing nodes, developers do not know the relevant configurations of different computing nodes. This information needs to be carried out on-site after the developers go to the site. Manual creation. However, manual creation will bring security issues (the root account may be used, etc.).

In addition, DAPP is deployed manually on-site, so the resources allocated when starting the application vary "from person to person". Different deployers use different computing node resources when deploying applications. This may eventually lead to unreasonable and uncontrollable allocation of resources, and neither the number of DAPPs that can be deployed on computing nodes nor the quality of deployment can be guaranteed. At the same time, DAPP deployment isolation is also uncontrollable during manual deployment. Since there is no standardized intervention for manual deployment, the application may be started directly when it is started, and sandbox isolation cannot be implemented for each application. This makes it possible that when an application has performance problems, it may cause the entire Compute node crash.

In view of the above problems, embodiments of this specification provide a blockchain-based distributed application deployment method and device. After the developer publishes the target application through the computing node used by the developer, the blockchain connected to the computing node The nodes in can upload the relevant information of the target application to the blockchain, and the computing nodes connected to other nodes in the blockchain can obtain the relevant information of the target application from the blockchain. When other computing nodes can deploy the target application, the other computing nodes can automatically obtain the installation package of the target application from the computing node that publishes the target application, and automatically complete the application deployment. This enables automatic deployment of target applications, improving deployment efficiency, security and stability.

Figure 1 is a schematic architectural diagram of a blockchain system provided in the embodiment of this specification. As shown in Figure 1, the blockchain includes, for example, node 1 to node 6, a total of 6 nodes. Each node can be any device, server or device cluster with computing and processing capabilities. The connections between nodes schematically represent P2P (Peer to Peer, point-to-point) connections.

These nodes can store the entire ledger, that is, store the status of all blocks and all accounts. Among them, each node in the blockchain can generate the same state in the blockchain by executing the same transaction, and each node in the blockchain can store the same state database. It can be understood that the blockchain shown in Figure 1 can be, but is not limited to, a consortium chain. In addition, although FIG. 1 shows that the blockchain includes 6 nodes, the embodiments of this specification are not limited to this, and may include other numbers of nodes. Specifically, the nodes included in the blockchain can meet Byzantine Fault Tolerance (BFT) requirements. The mentioned Byzantine fault tolerance requirements can be understood as meaning that Byzantine nodes can exist within the blockchain, but the blockchain does not reflect Byzantine behavior externally. Generally, some Byzantine fault-tolerant algorithms require the number of nodes to be greater than (3f+1), where f is the number of Byzantine nodes, such as the Practical Byzantine Fault Tolerance algorithm PBFT (Practical Byzantine Fault Tolerance).

Transactions in the blockchain field can refer to task units that are executed and recorded in the blockchain. Transactions usually include sending fields (From), receiving fields (To) and data fields (Data). Among them, when the transaction is a transfer transaction, the From field represents the account address that initiated the transaction (that is, initiated a transfer task to another account), the To field represents the account address that received the transaction (that is, received the transfer), and the Data field Include transfer amount. In the case of a transaction calling a smart contract in the blockchain, the From field indicates the account address that initiated the transaction, the To field indicates the account address of the contract called by the exchange, and the Data field includes the function name in the calling contract and the corresponding Data such as the incoming parameters of the function are used to obtain the code of the function from the blockchain and execute the code of the function when the transaction is executed.

The functions of smart contracts can be provided in the blockchain. Smart contracts on the blockchain are contracts that can be triggered and executed by transactions on the blockchain system. Smart contracts can be defined in the form of code. Calling a smart contract in the alliance chain is to initiate a transaction pointing to the smart contract address, allowing each node in the alliance chain network to run the smart contract code in a distributed manner. It should be noted that in addition to smart contracts that can be created by users, smart contracts can also be set by the system in the genesis block. This type of contract is generally called a creation contract. Generally, some blockchain data structures, parameters, properties and methods can be set in the genesis contract. In addition, accounts with system administrator rights can create system-level contracts or modify system-level contracts (referred to as system contracts). Among them, the system contract can be used to add data structures for different business data in the blockchain.

In the scenario of deploying a contract, for example, Bob sends a transaction containing information about creating a smart contract (i.e., deploying the contract) to the blockchain as shown in Figure 1. The data field of the transaction includes the code of the contract to be created ( Such as bytecode or machine code), the to field of the transaction is empty to indicate that the transaction is used to deploy the contract. After the nodes reach an agreement through the consensus mechanism, the contract address "0x6f8ae93..." of the contract is determined. Each node adds the contract account corresponding to the contract address of the smart contract in the state database, allocates the state storage corresponding to the contract account, and stores The contract code is saved in the state storage of the contract, so the contract is created successfully.

In the scenario of calling a contract, for example, Bob sends a transaction for calling a smart contract to the blockchain as shown in Figure 1. The from field of the transaction is the address of the account of the transaction initiator (Bob). "0x6f8ae93..." in the to field represents the address of the smart contract being called, and the data field of the transaction includes the method and parameters for calling the smart contract. After consensus is reached on the transaction in the blockchain, each node in the blockchain can execute the transaction respectively, thereby executing the contract respectively, and update the status database based on the execution of the contract.

In addition, after the smart contract is deployed on the blockchain, a corresponding contract account will be generated. This contract account generally has some states, which are defined by the state variables in the smart contract and generate new values when the smart contract is created and executed. Among them, contract accounts can be used to store status related to smart contracts. Once an event triggers the terms in the smart contract (execution conditions are met), the code can be executed automatically. In the blockchain, the relevant status of the contract is stored in the storage trie, and the hash value of the root node of the storage tree is stored in the above-mentioned storage_root, thereby locking all the status of the contract to the contract account through hash. The storage tree is also an MPT tree structure, which stores the key-value mapping from state addresses to state values. The address of a state is stored from the root node of the storage tree to the leaf nodes, and the value of a state is stored in a leaf node.

Continuing to refer to Figure 1, different nodes in the blockchain shown in Figure 1 can be responsible for docking with different computing nodes 10. Each computing node 10 may be, but is not limited to, used to perform calculation processing on data, etc., and transmit the processed results, etc. to the nodes in the blockchain connected to it. Each node in the blockchain can reach consensus with other nodes in the blockchain on the data obtained from the computing nodes it is connected to through the consensus mechanism. Among them, different computing nodes can establish communication connections through, but are not limited to, BTN (Blockchain Transmission Network), etc.

In this embodiment, an industry application middleware needs to be deployed on each computing node 10. Among them, developers can log in to the DAPP publishing website through the industry application middleware on the computing node and publish DAPP. Users can log in to the DAPP subscription website through the industry application middleware on the computing node and subscribe to DAPP.

For example, when releasing a DAPP, developers can upload the application information related to the DAPP to the blockchain through a computing node deployed with industry middleware, and store the DAPP installation package on the computing node. Among them, the application information of the DAPP may include one or more of the following: the node identification of the computing node where the industry application middleware is deployed, the network identification of the computing node in the network, the description information of the DAPP, the information associated with the DAPP and required The data structure of the business data on the chain, or the strategy for data flow in the network associated with DAPP, etc.

When subscribing to a DAPP, users can obtain the application information of the DAPP that the computing node can subscribe to from the blockchain through a computing node deployed with industry middleware; and, users can obtain the application information of the DAPP that the computing node can subscribe to through a computing node deployed with industry middleware and publish It communicates with the computing node of the DAPP it can subscribe to to obtain the installation package of the DAPP it can subscribe to. Then, the computing node used by the user that is deployed with industry middleware can deploy the DAPP based on the obtained DAPP installation package. After the computing node is deployed, the user can use the DAPP.

Therefore, using the point-to-point transmission network characteristics of the blockchain, after the developer publishes/updates the DAPP, the computing node used by the developer can automatically complete the distribution, and the computing node used by the user can automatically obtain the data that it can subscribe to DAPP installation package and complete the deployment of DAPP, so that developers do not need to manually go to each node to deploy and distribute DAPP, solving the resource distribution problem of distributed applications with multiple nodes, multiple applications, and multiple developers. , which improves the deployment efficiency, security and stability of DAPP.

The solutions provided in this specification will be described in detail below with reference to specific examples.

Figure 2 is a schematic flowchart of a blockchain-based distributed application deployment method provided in the embodiment of this specification. In Figure 2, the first computing node is deployed with the first industry application middleware, the second computing node is deployed with the second industry application middleware, and there is a first block in the blockchain that is connected to the first computing node. a chain node, and a second blockchain node connected to the second computing node. The first computing node may be a node used by users of DAPP, and the second computing node may be a node used by developers of DAPP. As shown in Figure 2, the method may include the following steps:

In S201, the second computing node obtains a publishing request for the target application, where the publishing request includes the first application information and the first installation package of the target application.

In this embodiment, the developer can log in to the website for publishing the target application through the second industry application middleware deployed in the second computing node, and submit a publishing request for the target application. In this way, the second computing node can obtain to a publish request to the target application. For example, the publishing request may include: the first application information and the first installation package of the target application. The first application information may include one or more of the following: connection information of the second computing node, description information of the target application, a data structure of business data associated with the target application and to be uploaded, or, associated with the target application Strategies for data flow in the network, etc. For example, the connection information of the second computing node may include: the node identification of the second computing node, the network identification of the second computing node in the network, and so on.

For example, the description information of the target application may include: the subscription type of the target application. Among them, the subscription type can include: mandatory subscription, limited subscription or open subscription. When the subscription type is mandatory subscription, the subscription scope can be one or more specific objects. At this time, only specific objects can subscribe to the application; when the subscription type is limited subscription, the subscription scope can be one or more specific objects. When the subscription type is open subscription, the subscription scope can be all objects, in which case all objects can subscribe to the application. For example, the subscription scope can be understood as the authorization information for the target application to authorize the computing node. For example, when the first computing node is included in the subscription scope, it indicates that the target application is authorized for the first computing node, that is, the first computing node can subscribe to the target application.

In S202, the second computing node uploads the first application information to the blockchain through the second blockchain node, and stores the first installation package.

In this embodiment, the second industry application middleware may send a transaction for calling the smart contract to the second blockchain node through the second computing node, and the data field in the transaction may include the first application information. After the second blockchain node obtains the transaction sent by the second computing node, it can reach consensus on the transaction with other nodes in the blockchain. After the nodes in the blockchain reach consensus on the transaction, each node in the blockchain can execute the transaction separately, thereby executing the smart contract respectively, and update the status database based on the execution of the smart contract, so that each node in the blockchain The corresponding state database may all have the first application information. At this time, the first application information is stored in the contract state of the smart contract. Thus, the second computing node uploads the first application information to the blockchain through the second blockchain node.

In addition, after obtaining the first installation package, the second computing node may store the first installation package locally.

In S203, the first computing node obtains the first application information from the blockchain.

In this embodiment, after the first application information is uploaded to the blockchain, the first computing node can obtain the first application information from the blockchain.

As a possible implementation method, the first computing node can send a query transaction for calling the smart contract to the first blockchain node in a polling manner through the first industry application middleware on it, and the query transaction includes the first The node ID of a compute node. This query transaction can be used to filter out applications authorized for the first computing node from the contract status of the smart contract. For example, when the target application is an application authorized for the first computing node, the query transaction can be understood as querying the first application information of the target application. After the first blockchain node obtains the query transaction sent by the first computing node, it can execute the query transaction, thereby filtering out the first query transaction from the contract status of the smart contract based on the node identification of the first computing node in the query transaction. The target applications authorized by the computing node are to filter out the target applications that the first computing node can subscribe to. For example, when the objects that can subscribe to the application in the application information of each application in the contract state include the first computing node, the target application can be filtered out from each application based on the node identifier of the first computing node, and the target application can be obtained. The first application information of the target application. Then, the first blockchain node can return the first application information to the first computing node. In this way, the first computing node obtains the first application information.

In S204, the first computing node determines whether it needs to deploy the target application based on the first application information.

In this embodiment, after the first computing node obtains the first application information, the first industry application middleware deployed on it can determine whether the target application needs to be deployed based on the subscription type in the first application information. When the subscription type is mandatory subscription, the first industry application middleware can determine that the target application needs to be deployed on the first computing node. At this time, the first computing node immediately deploys the target application. When the subscription type is limited subscription or open subscription, the first industry application middleware can ask the user through the first computing node whether to deploy the target application. After the user issues a deployment instruction, the first computing node needs to deploy the target application. For example, the first industry application middleware may control the display of query information on the user UI displayed by the first computing node, and the query information is used to query the user whether to deploy the target application.

In S205, if the target application needs to be deployed on the first computing node, the first computing node obtains the first installation package of the target application from the second computing node according to the connection information of the second computing node included in the first application information.

In this embodiment, the first computing node can obtain the connection information of the second computing node from the first application information, such as the node identification of the second computing node and the network identification of the second computing node in the network. Then, the first computing node may communicate with the second computing node through the BTN based on the connection information of the second computing node to obtain the installation package of the target application. For example, as shown in Figure 3, in S301, the first computing node may send an application acquisition request to the second computing node, and the application acquisition request may include the application identification of the target application. In S402, the second computing node may filter out the installation package of the target application from the installation packages of the application stored therein based on the application identifier of the target application, and send the installation package to the first computing node.

In S206, the first computing node deploys the target application based on the first installation package.

In this embodiment, after the first computing node obtains the first installation package of the target application, the first computing node dynamically configures and dynamically deploys the target application based on the first installation package to complete the deployment of the target application, thereby enabling use The user can use the target application on the first computing node.

Among them, when the first computing node is dynamically configured, based on its own software environment, the first computing node can generate an account and password for a database (such as mysql) for storing local data of the target application, and generate an account and password for storing the target application. The account and password of the application's cache data storage system (such as Redis). In addition, when dynamically configuring the first computing node, you can also configure startup commands, such as configuring startup resource occupancy, CPU, memory, startup port, sub-configuration files to be loaded, JVM commands, etc.

When the first computing node is dynamically deployed, you can use docker or k8s (kubernetes) to build an image to isolate the target application, thereby ensuring that the target application does not affect each other and other applications, and ensuring the safety of the first computing node. stability. After the image construction is completed, the first computing node can start the image and load the installation package of the target application to complete the installation. At this point, after the target application is released through the second computing node, the target application is automatically deployed on the first computing node.

In some embodiments, the blockchain shown in Figure 2 can represent any blockchain node in the blockchain.

It can be understood that although two computing nodes are shown in Figure 2, the embodiments of this specification are not limited thereto, and may include other numbers of computing nodes.

Based on the same concept as the foregoing method embodiments, the embodiments of this specification also provide a blockchain-based distributed application deployment device.

Illustratively, FIG. 4 is a schematic structural diagram of a blockchain-based distributed application deployment device provided in the embodiment of this specification. Wherein, the device can be deployed on the first computing node. As shown in Figure 4, the device 400 includes: an acquisition module 410, a judgment module 420 and a processing module 430. The acquisition module 410 is configured to acquire the first application information of the target application from the blockchain, where the first application information includes the connection information of the second computing node, and the first application information is uploaded to the blockchain through the second computing node. The determination module 420 is configured to determine whether the target application needs to be deployed based on the first application information. The acquisition module 410 is also configured to acquire the first installation package of the target application from the second computing node according to the connection information of the second computing node when the determination module 420 determines that the target application needs to be deployed. The processing module 430 is configured to deploy the target application based on the first installation package when the obtaining module 410 obtains the first installation package.

In a possible implementation, the first application information is stored in the contract state of the smart contract, and the first application information also includes authorization information for the target application to authorize the first computing node. The acquisition module 410 is specifically configured to: send a query transaction for calling the smart contract to the first blockchain node in the blockchain, and the query transaction is used to filter applications authorized for the first computing node from the contract status of the smart contract. , the first blockchain node is a node in the blockchain that is connected to the first computing node; and, obtain the first application information returned by the first blockchain node.

In a possible implementation, the first application information also includes one or more of the following: a data structure of business data associated with the target application that needs to be uploaded, or a data structure of data associated with the target application that flows in the network. Strategy.

In a possible implementation manner, the first application information also includes the subscription type of the target application.

Subscription types include mandatory subscription, limited subscription, or open subscription. The determination module 420 is specifically configured to determine whether the target application needs to be deployed based on the subscription type.

In one possible implementation, the processing module 430 is specifically configured to: generate an account and password for a database used to store local data of the target application, and deploy the target application based on the account and password.

For example, FIG. 5 is a schematic structural diagram of another blockchain-based distributed application deployment device provided in the embodiment of this specification. Wherein, the device can be deployed on the second computing node. As shown in Figure 5, the device 500 includes: an acquisition module 510 and a processing module 520. The acquisition module 510 is configured to obtain a release request for the target application, where the release request includes first application information and a first installation package of the target application, and the first application information includes connection information of the second computing node. The processing module 520 is configured to upload the first application information to the blockchain through a second blockchain node in the blockchain, and store the first installation package, where the second blockchain node is the same as in the blockchain. The node to which the second computing node is connected.

Illustratively, FIG. 6 is a schematic structural diagram of yet another blockchain-based distributed application deployment device provided in the embodiment of this specification. Among them, the device can be deployed at the first blockchain node. As shown in Figure 6, the device 600 includes: an acquisition module 610 and a processing module 620. Wherein, the acquisition module 610 is configured to receive a first transaction for calling a smart contract. The first transaction is sent to the blockchain by a second computing node connected to the second blockchain node. The first transaction includes the target application's information. The first application information includes the connection information of the second computing node, and the second computing node stores the first installation package of the target application. The processing module 620 is configured to store the first application information into the contract state of the smart contract according to the first transaction. In addition, the acquisition module 610 is further configured to receive a second transaction for calling the smart contract from the first computing node, and the second transaction is used for querying application information. The processing module 620 is further configured to send the first application information in the contract state to the first computing node according to the second transaction so that the first computing node obtains the first installation package of the target application from the second computing node according to the connection information.

In the 1990s, improvements in a technology could be clearly distinguished as hardware improvements (for example, improvements in circuit structures such as diodes, transistors, switches, etc.) or software improvements (improvements in method processes). However, with the development of technology, many improvements in today's method processes can be regarded as direct improvements in hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement of a method flow cannot be implemented using hardware entity modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic functions are determined by the user programming the device. Designers can program themselves to "integrate" a digital system on a PLD, instead of asking chip manufacturers to design and produce dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in program development and writing, and before compilation The original code must also be written in a specific programming language, which is called Hardware Description Language (HDL), and HDL is not just one kind, but there are many, 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., are currently the most commonly used The two are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that by simply logically programming the method flow using the above-mentioned hardware description languages and programming it into the integrated circuit, the hardware circuit that implements the logical method flow can be easily obtained.

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 (eg, software or firmware) executable by the (micro)processor. , logic gates, switches, Application Specific Integrated Circuit (ASIC), programmable logic controllers and embedded microcontrollers. Examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, For Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic. Those skilled in the art also know that in addition to implementing the controller in the form of pure computer-readable program code, the controller can be completely programmed with logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded logic by logically programming the method steps. Microcontroller, etc. to achieve the same function. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the means for implementing various functions can be considered as structures within hardware components as well as software modules implementing the methods.

The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a server system. Of course, this application does not rule out that with the development of computer technology in the future, the computer that implements the functions of the above embodiments may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular phone, a camera phone, a smart phone, or a personal digital assistant. , media player, navigation device, email device, game console, tablet, wearable device, or a combination of any of these devices.

Although one or more embodiments of this specification provide method operation steps as described in the embodiments or flow charts, more or fewer operation steps may be included based on conventional or non-inventive means. The sequence of steps listed in the embodiment is only one way of executing the sequence of many steps, and does not represent the only execution sequence. When the actual device or terminal product is executed, it may be executed sequentially or in parallel according to the methods shown in the embodiments or figures (for example, a parallel processor or a multi-thread processing environment, or even a distributed data processing environment). The terms "comprises," "comprises" or any other variation thereof are intended to cover a non-exclusive inclusion such that a process, method, product or apparatus including a list of elements includes not only those elements but also others not expressly listed elements, or also elements inherent to the process, method, product or equipment. Without further limitation, it does not exclude the presence of additional identical or equivalent elements in a process, method, product or apparatus including the stated elements. For example, if the words "first" and "second" are used to express names, they do not indicate any specific order.

For the convenience of description, when describing the above device, the functions are divided into various modules and described separately. Of course, when implementing one or more of this specification, the functions of each module can be implemented in the same or multiple software and/or hardware, or the modules that implement the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. . The device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes 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 device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce a use A device for realizing the functions specified in one process or multiple processes of the flowchart and/or one block or multiple blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions The device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device. Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-permanent storage in computer-readable media, random access memory (RAM) and/or non-volatile memory in the form of read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer-readable media includes both persistent and non-volatile, removable and non-removable media that can be implemented by any method or technology for storage of information. Information may be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media 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), and 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 disc (DVD) or other optical storage, Magnetic tape, magnetic tape storage, graphene storage or other magnetic storage devices or any other non-transmission medium can be used to store information that can be accessed by a computing device. As defined in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.

It should be understood by those skilled in the art that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, one or more embodiments of the present description may employ a computer program implemented 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. Product form.

One or more embodiments of this specification 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 specific tasks or implement specific abstract data types. One or more embodiments of the present description may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

Each embodiment in this specification is described in a progressive manner. The same and similar parts between the various embodiments can be referred to each other. Each embodiment focuses on its differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For relevant details, please refer to the partial description of the method embodiment. In the description of this specification, reference to the terms "one embodiment," "some embodiments," "an example," "specific examples," or "some examples" or the like means that specific features are described in connection with the embodiment or example. , structures, materials or features are included in at least one embodiment or example of this specification. In this specification, the schematic expressions of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the specific features, structures, materials or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, those skilled in the art may combine and combine different embodiments or examples and features of different embodiments or examples described in this specification unless they are inconsistent with each other.

The above descriptions are only examples of one or more embodiments of this specification, and are not intended to limit one or more embodiments of this specification. To those skilled in the art, various modifications and changes may be made to one or more embodiments of this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification shall be included in the scope of the claims.

Claims

A blockchain-based distributed application deployment method, the method is executed by a first computing node, including:

Obtain the first application information of the target application from the blockchain, the first application information includes the connection information of the second computing node, and the first application information is uploaded to the blockchain through the second computing node;

Based on the first application information, determine whether the target application needs to be deployed;

If the target application needs to be deployed, obtain the first installation package of the target application from the second computing node according to the connection information, and deploy the target application based on the first installation package.
The method of claim 1, wherein the first application information is stored in a contract state of a smart contract, and the first application information further includes authorization information for the target application to authorize the first computing node, Obtaining the first application information of the target application from the blockchain includes:

Send a query transaction for calling a smart contract to the first blockchain node in the blockchain, where the query transaction is used to filter applications authorized for the first computing node from the contract status of the smart contract. , the first blockchain node is a node in the blockchain that is connected to the first computing node;

Obtain the first application information returned by the first blockchain node.
The method according to claim 1 or 2, wherein the first application information further includes: a data structure of business data associated with the target application and to be uploaded, and/or a data structure associated with the target application. Strategies for data flow in the network.
The method according to claim 1 or 2, wherein the first application information further includes: a subscription type of the target application, the subscription type includes a mandatory subscription, a limited subscription or an open subscription. Application information, determining whether the target application needs to be deployed, including: based on the subscription type, determining whether the target application needs to be deployed.
The method according to claim 1 or 2, wherein the deploying the target application based on the first installation package includes:

Generate an account and password for a database that stores local data of the target application, and deploy the target application based on the account and password.
A blockchain-based distributed application deployment method, the method is executed by a second computing node, including:

Obtain a release request for the target application, the release request includes first application information and a first installation package of the target application, and the first application information includes connection information of the second computing node;

Upload the first application information to the blockchain through a second blockchain node in the blockchain, and store the first installation package, where the second blockchain node is the A node in the blockchain that is connected to the second computing node.
A blockchain-based distributed application deployment method, the method is executed by a first blockchain node, including:

Receive a first transaction for invoking a smart contract, the first transaction is sent to the blockchain by a second computing node connected to the second blockchain node, the first transaction includes a first application of the target application Information, the first application information includes connection information of the second computing node, and the first installation package of the target application is stored in the second computing node;

According to the first transaction, store the first application information in the contract state of the smart contract;

Receive a second transaction for invoking a smart contract from the first computing node, the second transaction being used to query application information;

The first application information in the contract state is sent to the first computing node according to the second transaction so that the first computing node obtains the application information from the second computing node according to the connection information. The first installation package of the target application.
A distributed application deployment device based on blockchain, deployed on the first computing node, the device includes:

The acquisition module is configured to obtain the first application information of the target application from the blockchain, the first application information includes the connection information of the second computing node, and the first application information is uploaded to the second computing node through the second computing node. The blockchain;

A judgment module configured to judge whether the target application needs to be deployed based on the first application information;

The acquisition module is further configured to acquire the first installation package of the target application from the second computing node according to the connection information when the determination module determines that the target application needs to be deployed;

A processing module configured to deploy the target application based on the first installation package when the acquisition module obtains the first installation package.
A blockchain-based distributed application deployment device, deployed on the second computing node, the device includes:

Obtaining module, configured to obtain a release request for a target application, the release request includes first application information and a first installation package of the target application, the first application information includes connection information of the second computing node ;

A processing module configured to upload the first application information to the blockchain through a second blockchain node in the blockchain, and store the first installation package, wherein the second block A chain node is a node in the blockchain that is connected to the second computing node.
A distributed application deployment device based on blockchain, deployed on the first blockchain node, including:

An acquisition module configured to receive a first transaction for invoking a smart contract, the first transaction being sent to the blockchain by a second computing node connected to the second blockchain node, the first transaction including a target The first application information of the application, the first application information includes the connection information of the second computing node, and the first installation package of the target application is stored in the second computing node;

A processing module configured to store the first application information in the contract state of the smart contract according to the first transaction;

The acquisition module is further configured to receive a second transaction for calling the smart contract from the first computing node, where the second transaction is used to query application information;

The processing module is further configured to send the first application information in the contract state to the first computing node according to the second transaction so that the first computing node obtains the information from the connection information based on the connection information. Obtain the first installation package of the target application at the second computing node.
A computer-readable storage medium with a computer program stored thereon. When the computer program is executed in a computing device, the computing device performs the method described in any one of claims 1 to 5, or performs claim 6 The method described in claim 7, or perform the method described in claim 7.
A computing device, including a memory and a processor. A computer program is stored in the memory. When the processor executes the computer program, it implements the method described in any one of claims 1 to 5, or executes the claim. The method described in claim 6, or performing the method described in claim 7.