Reliability Patterns in Permissioned Blockchain Systems
summary
Covers concrete patterns for Hyperledger Fabric deployments: recommended cluster sizes (three orderers for Raft, three-plus for BFT to tolerate f failures), peer counts per org (2–3), Kubernetes anti‑affinity, block‑size tuning, endorsement policy examples (any two-of-three), rolling upgrades, chaos testing and real failure postmortems (leader elections, certificate expiry). Shows monitoring stack and alerts (Prometheus + Grafana), tradeoffs between Raft and BFT ordering, operational configs and a sample Hyperledger Fabric topology and Prometheus + Grafana alerts.
AI-written summary · about
chapters (11)
- 0:00Introduction to Reliability Patterns
- 1:04Session Overview
- 1:55Understanding Hyperledger Fabric
- 6:07Fault Tolerance in Node Clusters
- 9:21Byzantine Fault Tolerance
- 11:39Handling Network Partitions
- 13:10Performance Tuning for High Availability
- 15:45Monitoring and Alerting Strategies
- 16:59Real-World Failure Scenarios
- 18:55Industry Use Cases and Best Practices
- 20:43Conclusion and Final Thoughts
related talks
35mManaging and Securing Blockchain Applications on Kubernetes
04mRebuilding trust through blockchains and open source
53mHyperledger Fabric: The Enterprise Blockchain Framework
41mVulnerabilities in the Hyperledger Fabric Platform
01h 07mBlockchain for Developer - What's behind the hype?
35mCreating your First Smart Contract on Hyperledger Fabric!- 01h 07mBlockchain for Developer - What's behind the hype?
35mCreating your First Smart Contract on Hyperledger Fabric!