Book Image

Blockchain with Hyperledger Fabric - Second Edition

By : Nitin Gaur, Anthony O'Dowd, Petr Novotny, Luc Desrosiers, Venkatraman Ramakrishna, Salman A. Baset
Book Image

Blockchain with Hyperledger Fabric - Second Edition

By: Nitin Gaur, Anthony O'Dowd, Petr Novotny, Luc Desrosiers, Venkatraman Ramakrishna, Salman A. Baset

Overview of this book

Blockchain with Hyperledger Fabric - Second Edition is a refreshed and extended version of the successful book on practical Hyperledger Fabric blockchain development. This edition includes many new chapters, alongside comprehensive updates and additions to the existing ones. Entirely reworked for Hyperledger Fabric version 2, this edition will bring you right up to date with the latest in blockchain. Using a real-world Trade Finance and Logistics example, with working code available on GitHub, you’ll really understand both how and why Hyperledger Fabric can be used to maximum effect. This book is your comprehensive guide and reference to explore and build blockchain networks using Hyperledger Fabric version 2. This edition of the book begins by outlining the evolution of blockchain, including an overview of relevant blockchain technologies. Starting from first principles, you’ll learn how to design and operate a permissioned blockchain network based on Hyperledger Fabric version 2. You will learn how to configure the main architectural components of a permissioned blockchain network including Peers, Orderers, Certificate Authorities, Channels, and Policies. You’ll then learn how to design, develop, package, and deploy smart contracts, and how they are subsequently used by applications. This edition also contains chapters on DevOps, blockchain governance, and security, making this your go-to book for Hyperledger Fabric version 2.
Table of Contents (18 chapters)
Another Book You May Enjoy

Continuous delivery

The terms CI and CD are too often conflated into CI/CD, causing the nuance between the two processes to be lost. Hopefully, by the end of this chapter, we will have clarified the two.

Up until this point, our attention has been primarily on CI, the process of building and testing the software components of the solution. If CI is there to ensure the quality of our software, CD ensures the consistency of the configuration of our infrastructure.

In the traditional data center world, workloads tended to be long-lived, and the management of the configuration was an eternal battle as manual intervention created an opportunity for configuration drift and made systems hard to maintain and troubleshoot.

Now, with the advent of software-defined infrastructure, the cloud, Docker, and Kubernetes, there is a big push toward automation. Through automation, we can now define infrastructure through declarative languages, and we can manage those configurations as assets...