WO2023240933A1 - Procédé et appareil de déploiement d'application distribuée sur la base d'une chaîne de blocs - Google Patents

Procédé et appareil de déploiement d'application distribuée sur la base d'une chaîne de blocs Download PDF

Info

Publication number
WO2023240933A1
WO2023240933A1 PCT/CN2022/135258 CN2022135258W WO2023240933A1 WO 2023240933 A1 WO2023240933 A1 WO 2023240933A1 CN 2022135258 W CN2022135258 W CN 2022135258W WO 2023240933 A1 WO2023240933 A1 WO 2023240933A1
Authority
WO
WIPO (PCT)
Prior art keywords
blockchain
application
computing node
target application
node
Prior art date
Application number
PCT/CN2022/135258
Other languages
English (en)
Chinese (zh)
Inventor
庞洋
王志伟
孙兵兵
Original Assignee
蚂蚁区块链科技(上海)有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 蚂蚁区块链科技(上海)有限公司 filed Critical 蚂蚁区块链科技(上海)有限公司
Publication of WO2023240933A1 publication Critical patent/WO2023240933A1/fr

Links

Images

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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Definitions

  • 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.
  • Blockchain is a new application model of computer technology such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm.
  • 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.
  • Blockchain can generally be divided into three categories: public blockchain, private blockchain and consortium blockchain according to different application scenarios and user needs.
  • 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.
  • 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
  • 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.
  • 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 is also configured to send 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.
  • a seventh aspect of this specification provides a computer-readable storage medium on which a computer program is stored.
  • 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.
  • the processor executes the computer program, the first aspect, the second aspect or the third aspect are implemented. described method.
  • 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.
  • 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.
  • FIG. 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.
  • DAPP distributed application
  • N the number of distributed application developers
  • M the number of distributed application developers
  • P the number of nodes that need to be deployed
  • O 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.
  • 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.
  • 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.
  • embodiments of this specification provide a blockchain-based distributed application deployment method and device.
  • 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.
  • 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.
  • FIG 1 is a schematic architectural diagram of a blockchain system provided in the embodiment of this specification.
  • 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.
  • 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.
  • the blockchain shown in Figure 1 can be, but is not limited to, a consortium chain.
  • 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.
  • the nodes included in the blockchain can meet Byzantine Fault Tolerance (BFT) requirements.
  • BFT Byzantine Fault Tolerance
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • smart contracts can also be set by the system in the genesis block. This type of contract is generally called a creation contract.
  • some blockchain data structures, parameters, properties and methods can be set in the genesis contract.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • different computing nodes can establish communication connections through, but are not limited to, BTN (Blockchain Transmission Network), etc.
  • an industry application middleware needs to be deployed on each computing node 10.
  • 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.
  • 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.
  • 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.
  • 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.
  • Figure 2 is a schematic flowchart of a blockchain-based distributed application deployment method provided in the embodiment of this specification.
  • the first computing node is deployed with the first industry application middleware
  • the second computing node is deployed with the second industry application middleware
  • 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
  • the second computing node may be a node used by developers of DAPP.
  • the method may include the following steps:
  • 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.
  • 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.
  • the second computing node can obtain to a publish request to the target application.
  • 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.
  • 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.
  • the description information of the target application may include: the subscription type of the target application.
  • the subscription type can include: mandatory subscription, limited subscription or open 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.
  • the subscription scope can be all objects, in which case all objects can subscribe to the application.
  • 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.
  • the second computing node uploads the first application information to the blockchain through the second blockchain node, and stores the first installation package.
  • 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.
  • 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.
  • 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.
  • the first application information is stored in the contract state of the smart contract.
  • the second computing node uploads the first application information to the blockchain through the second blockchain node.
  • the second computing node may store the first installation package locally.
  • the first computing node obtains the first application information from the blockchain.
  • the first computing node can obtain the first application information from the blockchain.
  • 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.
  • 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.
  • the first blockchain node 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.
  • the first computing node determines whether it needs to deploy the target application based on 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.
  • 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.
  • the first computing node immediately deploys the target application.
  • 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.
  • the first computing node needs to deploy the target application.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 first computing node deploys the target application based on the first installation package.
  • the first computing node 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.
  • the first computing node 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).
  • startup commands such as configuring startup resource occupancy, CPU, memory, startup port, sub-configuration files to be loaded, JVM commands, etc.
  • the first computing node 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.
  • docker or k8s tunneles
  • the blockchain shown in Figure 2 can represent any blockchain node in the blockchain.
  • the embodiments of this specification also provide a blockchain-based distributed application deployment device.
  • FIG. 4 is a schematic structural diagram of a blockchain-based distributed application deployment device provided in the embodiment of this specification.
  • the device can be deployed on the first computing node.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 5 is a schematic structural diagram of another blockchain-based distributed application deployment device provided in the embodiment of this specification.
  • the device can be deployed on the second computing node.
  • 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.
  • FIG. 6 is a schematic structural diagram of yet another blockchain-based distributed application deployment device provided in the embodiment of this specification.
  • the device can be deployed at the first blockchain node.
  • the device 600 includes: an acquisition module 610 and a processing module 620.
  • 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.
  • 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.
  • PLD Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • HDL Hardware Description Language
  • 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.
  • 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.
  • the controller 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.
  • 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.
  • the functions are divided into various modules and described separately.
  • 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.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented.
  • 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.
  • 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.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile 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.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash random access memory
  • 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.
  • PRAM phase change memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • RAM random access memory
  • read-only memory read-only memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory or other memory technology
  • compact disc read-only memory CD-ROM
  • DVD digital versatile disc
  • 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.
  • computer-readable media does not include transitory media, such as modulated data signals and carrier waves.
  • 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.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types.
  • program modules may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network.
  • program modules may be located in both local and remote computer storage media including storage devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Computing Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

Les modes de réalisation de la présente description concernent un procédé et un appareil de déploiement d'application distribuée sur la base d'une chaîne de blocs. Le procédé comprend : l'acquisition, par un premier nœud informatique, dans une chaîne de blocs, de premières informations d'application d'une application cible, les premières informations d'application comprenant des informations de connexion d'un second nœud informatique, et les premières informations d'application étant téléchargées vers la chaîne de blocs au moyen du second nœud informatique ; le fait de déterminer, par le premier nœud informatique, sur la base des premières informations d'application, s'il est nécessaire de déployer l'application cible ; et s'il est nécessaire de déployer l'application cible, l'acquisition, par le premier nœud informatique auprès du second nœud informatique et selon les informations de connexion du second nœud informatique, d'un premier progiciel de l'application cible, et le déploiement de l'application cible. De cette façon, après qu'un second nœud informatique libère une application cible, un premier nœud informatique peut déployer de manière automatique et dynamique l'application cible de sorte que l'efficacité, la sécurité et la stabilité de déploiement de l'application cible sont améliorées.
PCT/CN2022/135258 2022-06-14 2022-11-30 Procédé et appareil de déploiement d'application distribuée sur la base d'une chaîne de blocs WO2023240933A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210668623.0 2022-06-14
CN202210668623.0A CN115098114A (zh) 2022-06-14 2022-06-14 一种基于区块链的分布式应用部署方法及装置

Publications (1)

Publication Number Publication Date
WO2023240933A1 true WO2023240933A1 (fr) 2023-12-21

Family

ID=83290219

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/135258 WO2023240933A1 (fr) 2022-06-14 2022-11-30 Procédé et appareil de déploiement d'application distribuée sur la base d'une chaîne de blocs

Country Status (2)

Country Link
CN (1) CN115098114A (fr)
WO (1) WO2023240933A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115098114A (zh) * 2022-06-14 2022-09-23 蚂蚁区块链科技(上海)有限公司 一种基于区块链的分布式应用部署方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107077557A (zh) * 2016-12-29 2017-08-18 深圳前海达闼云端智能科技有限公司 软件应用程序发布和验证的方法及装置
CN108984784A (zh) * 2018-07-26 2018-12-11 百度在线网络技术（北京）有限公司 基于区块链网络的应用实现方法、装置、设备和存储介质
CN111984271A (zh) * 2020-08-27 2020-11-24 北京海益同展信息科技有限公司 一种区块链应用程序处理方法、装置及区块链应用系统
CN115098114A (zh) * 2022-06-14 2022-09-23 蚂蚁区块链科技(上海)有限公司 一种基于区块链的分布式应用部署方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107077557A (zh) * 2016-12-29 2017-08-18 深圳前海达闼云端智能科技有限公司 软件应用程序发布和验证的方法及装置
CN108984784A (zh) * 2018-07-26 2018-12-11 百度在线网络技术（北京）有限公司 基于区块链网络的应用实现方法、装置、设备和存储介质
CN111984271A (zh) * 2020-08-27 2020-11-24 北京海益同展信息科技有限公司 一种区块链应用程序处理方法、装置及区块链应用系统
CN115098114A (zh) * 2022-06-14 2022-09-23 蚂蚁区块链科技(上海)有限公司 一种基于区块链的分布式应用部署方法及装置

Also Published As

Publication number Publication date
CN115098114A (zh) 2022-09-23

Similar Documents

Publication Publication Date Title
US11138030B2 (en) Executing code referenced from a microservice registry
EP3761170B1 (fr) Procédé et appareil de création de machine virtuelle
US10225335B2 (en) Apparatus, systems and methods for container based service deployment
US20120158819A1 (en) Policy-based application delivery
WO2022037612A1 (fr) Procédé de fourniture de service de construction d'applications, et plate-forme de construction d'applications, procédé de déploiement d'applications et système
WO2023231345A1 (fr) Procédé de regroupement d'une pluralité de transactions, et nœud de chaîne de blocs
US20210409346A1 (en) Metadata driven static determination of controller availability
US9336020B1 (en) Workflows with API idiosyncrasy translation layers
WO2023231336A1 (fr) Procédé d'exécution de transaction et nœud de chaîne de blocs
WO2024001024A1 (fr) Procédé d'exécution d'une transaction dans un système de chaîne de blocs, et système et nœuds de chaîne de blocs
US20150012669A1 (en) Platform runtime abstraction
WO2023160083A1 (fr) Procédé d'exécution de transactions, blockchain, nœud maître et nœud esclave
WO2023185058A1 (fr) Procédé et système de déploiement de code de chaîne dans une chaîne de blocs de consortium
WO2023160085A1 (fr) Procédé d'exécution de transaction, chaîne de blocs, nœud maître et nœud esclave
US11381638B1 (en) System and method for parallel execution of activites in an integration flow
US20220214931A1 (en) System and method for exposing features of integration platform adapters as first-class actions in an orchestration template
WO2023240933A1 (fr) Procédé et appareil de déploiement d'application distribuée sur la base d'une chaîne de blocs
WO2023185054A1 (fr) Procédé et système de déploiement de code de chaîne dans une chaîne d'alliance
WO2023231335A1 (fr) Procédé d'exécution d'une transaction dans une chaîne de blocs, et nœud maître de chaîne de blocs
WO2024001032A1 (fr) Procédé d'exécution d'une transaction dans un système de chaîne de blocs, et système et nœuds de chaîne de blocs
WO2023185055A1 (fr) Procédé et système de déploiement de code de chaîne dans une chaîne d'alliance
WO2023231342A1 (fr) Procédé et appareil pour exécuter automatiquement un contrat sur la base d'un état variable
WO2024001025A1 (fr) Procédé de nettoyage de données en mémoire cache de pré-exécution et nœud de chaîne de blocs
US9628401B2 (en) Software product instance placement
US11178216B2 (en) Generating client applications from service model descriptions

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22946599

Country of ref document: EP

Kind code of ref document: A1