i
Search icon

Blockchain Complete Guide  

Self Learning   /   Study Material   /   Blockchain Application Architecture
Previous
Next

Blockchain Application Architecture

As we understand by now, blockchain consists of a network of multiple nodes (node is a computer).

  • Blockchain Protocol This is the bottom-most layer and mainly does functions of providing decentralised consensus among various nodes.

There are several tasks that different parties need to agree upon like "Is this a right username? ", "Is this transaction valid?" , "Is this a valid identity?"

In a typical application architecture, you don't need consensus among parties as consensus was provided by Third-party intermediary.

  • Data Storage & Content Delivery we will probably need storage and blockchain is not always the best one to use because of speed and costs in typical application architecture; we have Google Cloud, AWS, Microsoft Azure for data storage with central authority over data. But for decentralised data architecture, we needed a decentralised version of storage. So, we have Swarm, IPFS (Interplanetary File System) etc. for this.

  • Smart Contract is used for computation

On top of smart contract, application-level constructs identity, AI could be added to make a DApp

  • Consumer-Facing Interface which holds your UI works probably in a browser and processes the DApp and Storage into something that a user can use.

  • Decentralised Application (DApp) which is built on blockchain and this can be a public chain or a private chain or both. Cryptokitty, Provenance are few such DApps.

Architecture has several pros and cons

Cons:

  • Less Throughput As of 2018, Bitcoin is processing three transactions per second, Ethereum with five and Uber (car ride-sharing app) gives 12 rides a second

  • scalability challenges

Pros:

  • Secure

  • Data Democratization

  • Value-based currency

© All rights Reserved | SelfLearning.io