https://github.com/gcp-development/event-streaming-platform
Event Streaming Platform (Blockchain)
https://github.com/gcp-development/event-streaming-platform
blockchain event-driven-architecture kafka kafka-streams kubernetes minikube proof-of-stake web3
Last synced: about 1 month ago
JSON representation
Event Streaming Platform (Blockchain)
- Host: GitHub
- URL: https://github.com/gcp-development/event-streaming-platform
- Owner: gcp-development
- License: mit
- Created: 2022-11-27T06:54:59.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2023-02-06T07:20:19.000Z (over 3 years ago)
- Last Synced: 2025-03-26T11:32:17.423Z (about 1 year ago)
- Topics: blockchain, event-driven-architecture, kafka, kafka-streams, kubernetes, minikube, proof-of-stake, web3
- Language: Java
- Homepage:
- Size: 311 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Event Streaming Platform (Blockchain)
## Motivation
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.
## Table of Contents
### Kafka and Kubernetes
Apache Kafka is frequently deployed on the [Kubernetes](https://kubernetes.io/) 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:
### Blockchain
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 overview
- 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 overview
- 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.
##### Consensus Mechanism
[Validators](https://github.com/gcp-development/event-streaming-platform/blob/main/basic-blockchain/src/main/java/org/blockchain/Validator.java)
In Proof of Stake blockchains, validators are selected to produce the next [block](https://github.com/gcp-development/event-streaming-platform/blob/main/basic-blockchain/src/main/java/org/blockchain/Block.java) based on their stake. Designed with [random functions](https://github.com/gcp-development/event-streaming-platform/blob/main/basic-blockchain/src/main/java/org/blockchain/ParticipantsPool.java#L53) in order to make the selection more fairer,because a larger amount staked by a [validator](https://github.com/gcp-development/event-streaming-platform/blob/main/basic-blockchain/src/main/java/org/blockchain/Validator.java) could give them a higher chance of producing the next [block](https://github.com/gcp-development/event-streaming-platform/blob/main/basic-blockchain/src/main/java/org/blockchain/Block.java). Proposed [blocks](https://github.com/gcp-development/event-streaming-platform/blob/main/basic-blockchain/src/main/java/org/blockchain/Block.java) by [validators](https://github.com/gcp-development/event-streaming-platform/blob/main/basic-blockchain/src/main/java/org/blockchain/Validator.java) are then propagated to the rest of the network, who verify and add the approved [block](https://github.com/gcp-development/event-streaming-platform/blob/main/basic-blockchain/src/main/java/org/blockchain/Block.java) to the blockchain.
Proof of Stake(PoS)
In order to participate in PoS, the [validators](https://github.com/gcp-development/event-streaming-platform/blob/main/basic-blockchain/src/main/java/org/blockchain/Validator.java) has to produce some stake. In PoS the validators are selected in terms of some [selection algorithm](https://github.com/gcp-development/event-streaming-platform/blob/main/basic-blockchain/src/main/java/org/blockchain/ParticipantsPool.java#L53) and the amount of stake locked in the network [(ParticipantsPool)](https://github.com/gcp-development/event-streaming-platform/blob/main/basic-blockchain/src/main/java/org/blockchain/ParticipantsPool.java) and only then that [selected validator](https://github.com/gcp-development/event-streaming-platform/blob/main/basic-blockchain/src/main/java/org/blockchain/ParticipantsPool.java#L53) will be allowed to add the [block](https://github.com/gcp-development/event-streaming-platform/blob/main/basic-blockchain/src/main/java/org/blockchain/Block.java). If the validator founds to be malicious, then they will lose all their stake.
### Implementation
Transactions Producer
->This [Java project](https://github.com/gcp-development/event-streaming-platform/tree/main/transactions-producer) will create the transactions for our basic blockchain.
Block Processor
->This [Java project](https://github.com/gcp-development/event-streaming-platform/tree/main/blocks-consumer) will process the transactions and create the new blocks for our basic blockchain.
Blocks Consumer
->This [Java project](https://github.com/gcp-development/event-streaming-platform/tree/main/blocks-consumer) will consume the blocks.
Basic Blockchain
->This [Java project](https://github.com/gcp-development/event-streaming-platform/tree/main/basic-blockchain) this library(JAR) contains the objects that form a basic blockchain.
##### 1) Run the blocks-consumer
As a prerequisite the [basic-blockchain project](https://github.com/gcp-development/event-streaming-platform/tree/main/basic-blockchain) needs to create the JAR which the other projects will use.
Open the [blocks-consumer project](https://github.com/gcp-development/event-streaming-platform/tree/main/blocks-consumer) with [Intellij community](https://www.jetbrains.com/idea/download/#section=linux) 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](https://logging.apache.org/log4j/2.x/).
##### 2) Run the block-processor
Open the [block-processor project](https://github.com/gcp-development/event-streaming-platform/tree/main/block-processor) with [Intellij community](https://www.jetbrains.com/idea/download/#section=linux) and run the project.
For troubleshooting any issue look at the logs generated by the [log4j](https://logging.apache.org/log4j/2.x/).
##### 3) Run the transactions-producer
Open the [transactions-producer project](https://github.com/gcp-development/event-streaming-platform/tree/main/transactions-producer) with [Intellij community](https://www.jetbrains.com/idea/download/#section=linux) and run the project.
For troubleshooting any issue look at the logs generated by the [log4j](https://logging.apache.org/log4j/2.x/).
The [transactions-producer project](https://github.com/gcp-development/event-streaming-platform/tree/main/transactions-producer) will insert 15 transactions in the transactions topic. This transactions topic is subscribed by the [block-processor project](https://github.com/gcp-development/event-streaming-platform/tree/main/block-processor) and the blocks created inserted in the blockchain topic.
The run windows should look like this.
The [blocks-consumer project](https://github.com/gcp-development/event-streaming-platform/tree/main/blocks-consumer) 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](https://martinfowler.com/articles/201701-event-driven.html)
[Benchmarking Apache Kafka: 2 Million Writes Per Second (On Three Cheap Machines)](https://engineering.linkedin.com/kafka/benchmarking-apache-kafka-2-million-writes-second-three-cheap-machines)
[Peercoin Introduction to Proof-of-Stake](https://www.peercoin.net/docs/proof-of-stake)