Blockchain and Kafka are complementary, Kafka and the notion of blockchain share many traits, such as immutability, replication, distribution, and the decoupling of applications. This complementary relationship means that we are able to extend the functionality of a given DLT(distributed ledger technology) through sidechain or off-chain activities, such as analytics, integrations with traditional enterprise systems, or even the integration of certain chains and ledgers.
Apache Kafka is frequently deployed on the Kubernetes management system, which is used to automate deployment, scaling, and operation of containers across clusters of hosts. Cloud-native applications are independent, loosely coupled, and distributed services that deliver high scalability via the cloud. In the same way, the event-driven applications built on Kafka are loosely coupled and designed to scale across a distributed hybrid cloud environment.
By integrating these technologies, this PoC creates a platform for demonstrate blockchain concepts in a simple and easy way.
Souce Code:
What is Blockchain?
- Blockchain is a transaction record database that is distributed, permission less and maintained around the world by a network of nodes.
- Blockchain has a distributed group of nodes that oversee the network.
- Blockchain uses decentralized technologies to provide peer-to-peer, permissionless, and immutable network to store transactions.
A blockchain network have the following characteristics:
- No Central Authority
- Verifiability and Auditability
- Disintermediation
- Confidentiality and Integrity
- Robustness
A blockchain network have the following benefits:
- No Third-Party Intermediaries
- Greater Transparency
- High Availability
- High Security
- Faster Dealings and Cost Savings
- Improved Traceability
- Block version, version number of the block.
- Previous block hash, the hash of the previous block.
- Merkle tree root hash, Each transaction in the block is hashed and stored in a tree-like structure such that each hash is linked to its parent.
- nBits, encoding of the block target. A block will be valid only if the hash of its header is below the target value.
- Nonce, a variable decided by the miner creating the block changed In order to get a block hash under target value.
- Timestamp, value is a source of variation for the block hash.
- Blockchain contains a list of blocks cryptographically connect to the previous block.
- The blocks are connected such that if there is any change in block(n-1) the connection between the next block will break.
- This makes very hard to change any data in blockchain.
- Each block contains set of transactions data that is linked in the next blocks so that anyone can trace the origin of data.
In Proof of Stake blockchains, validators are selected to produce the next block based on their stake. Designed with random functions in order to make the selection more fairer,because a larger amount staked by a validator could give them a higher chance of producing the next block. Proposed blocks by validators are then propagated to the rest of the network, who verify and add the approved block to the blockchain.
Proof of Stake(PoS)
In order to participate in PoS, the validators has to produce some stake. In PoS the validators are selected in terms of some selection algorithm and the amount of stake locked in the network (ParticipantsPool) and only then that selected validator will be allowed to add the block. If the validator founds to be malicious, then they will lose all their stake.
Transactions Producer
->This Java project will create the transactions for our basic blockchain.
Block Processor
->This Java project will process the transactions and create the new blocks for our basic blockchain.
Blocks Consumer
->This Java project will consume the blocks.
Basic Blockchain
->This Java project this library(JAR) contains the objects that form a basic blockchain.
As a prerequisite the basic-blockchain project needs to create the JAR which the other projects will use.
Open the blocks-consumer project with Intellij community and run the project.
The listener will subscribe to the blockchain topic to consume any message saved there.
For troubleshooting any issue look at the logs generated by the log4j.
Open the block-processor project with Intellij community and run the project.
For troubleshooting any issue look at the logs generated by the log4j.
Open the transactions-producer project with Intellij community and run the project.
For troubleshooting any issue look at the logs generated by the log4j.
The transactions-producer project will insert 15 transactions in the transactions topic. This transactions topic is subscribed by the block-processor project and the blocks created inserted in the blockchain topic.
The run windows should look like this.
The blocks-consumer project is subscribed to the blockchain topic which will read any message insert into the blockchain topic.
The run windows should look like this.
The Blockchain created.
Source Code:
References:
Event-Driven
Benchmarking Apache Kafka: 2 Million Writes Per Second (On Three Cheap Machines)
Peercoin Introduction to Proof-of-Stake
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent