Book Image

Blockchain for Enterprise

By : Narayan Prusty
Book Image

Blockchain for Enterprise

By: Narayan Prusty

Overview of this book

The increasing growth in blockchain use is enormous, and it is changing the way business is done. Many leading organizations are already exploring the potential of blockchain. With this book, you will learn to build end-to-end enterprise-level decentralized applications and scale them across your organization to meet your company's needs. This book will help you understand what DApps are and how the blockchain ecosystem works, via real-world examples. This extensive end-to-end book covers every blockchain aspect for business and for developers. You will master process flows and incorporate them into your own enterprise. You will learn how to use J.P. Morgan’s Quorum to build blockchain-based applications. You will also learn how to write applications that can help communicate enterprise blockchain solutions. You will learn how to write smart contracts that run without censorship and third-party interference. Once you've grasped what a blockchain is and have learned about Quorum, you will jump into building real-world practical blockchain applications for sectors such as payment and money transfer, healthcare, cloud computing, supply chain management, and much more.
Table of Contents (14 chapters)
Title Page
Packt Upsell

Raft consensus

Let's see how the Raft consensus protocol works at a level which will make us comfortable enough to build DApps. We won't go in depth into Raft as it's not necessary.

Raft is used in a semi-trusted network, and there is a desire for faster blocktimes (on the order of milliseconds instead of seconds) and single confirmation (the absence of regular forks).

Every node in the network keeps a list of all other nodes in the network regardless of whether they are up and running or not. A server in a Raft cluster is either a leader or a follower, and can be a candidate in the case of an election, which happens when the leader is unavailable. There can be only one leader at a time. The leader is responsible for creating and sending blocks to the followers. It regularly informs the followers of its existence by sending a heartbeat message. Each follower has a timeout (typically between 150 and 300 ms) called the election timeout, in which it expects the heartbeat from the leader. Every...