A Hitchhiker’s Guide to Deploying Hyperledger Fabric on Kubernetes

Join us Wednesday, September 26, 2018 9:00 a.m. Pacific for an introductory webinar showing how to deploy Hyperledger Fabric.

Deploying a multi-component system like Hyperledger Fabric to production is challenging. Join us Wednesday, September 26, 2018 9:00 a.m. Pacific for an introductory webinar, presented by Alejandro (Sasha) Vicente Grabovetsky and Nicola Paoli of AID:Tech.

Why should you care?

Hyperledger Fabric is rather awesome, but deploying a distributed network has been known to give headaches and even migraines. In this talk, we will not be providing you with a guillotine that forever gets rid of these headaches, but instead we will talk you through some tools that can help you deploy a functioning, production-ready Hyperledger Fabric network on a Kubernetes cluster.

Who should attend?

Ideally, you are a Dev, an Ops or a DevOps interested in learning more about how to deploy Hyperledger Fabric to Kubernetes.

You might know a little bit about Hyperledger Fabric and about Docker containers and Kubernetes. We assume limited knowledge and will do our best to as possible and explain and demystify all the components along the way.

What we will talk about?

In this webinar, we will lower the threshold so that you can deploy your very own Hyperledger Fabric network onto Kubernetes. So what is each of these?

Hyperledger Fabric is a permissioned (unlike the permissionless Ethereum network) framework, allowing you to create consortium Blockchain networks, where one or more organisations share an immutable ledger of records and smart contracts (called “chaincode” in Hyperledger Fabric).

Kubernetes is a platform for deploying microservices (i.e. containerised applications, typically using Docker) applications on a cluster, such that the applications:

use fewer resources than when using dedicated (bare metal or virtual) machines for each component,

are self-healing, such that failed containers are restarted

and are configured in a declarative rather than procedural way, making them robust

We do this by using a set of Helm Charts. Rather than using a monolithic Helm Chart for the whole deployment, we use separate charts for each Hyperledger Fabric component, namely the Certificate Authority, Peer, CouchDB and Orderer. We demonstrate how to get these charts working together to provide a unified blockchain system.

Along the way, we will explain the different concepts you need to understand your Hyperledger Fabric network:

What is a Certificate Authority?

Why is the network split across Orderers and Peers?

And what are CouchDB and Apache Kafka doing in all of this?

We’ll also guide you in the right direction to other resources you can look at to expand your understanding on how Hyperledger Fabric works, including: