Technical introduction to Hyperledger's Fabric
•Download as PPT, PDF•
11 likes•3,540 views
This document provides an overview of Hyperledger Fabric, an open source blockchain framework. It discusses key concepts like blockchain, Bitcoin, and Ethereum. It then explains core components of Hyperledger Fabric like chaincode, peers, and the transaction flow. The document also briefly touches on consensus algorithms, practical Byzantine fault tolerance, and the Hyperledger roadmap. It directs readers to additional resources on Altoros' website for more information on Hyperledger.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (19)
Similar to Technical introduction to Hyperledger's Fabric
Similar to Technical introduction to Hyperledger's Fabric (20)
More from Altoros
More from Altoros (20)
Recently uploaded
Recently uploaded (20)
Technical introduction to Hyperledger's Fabric
- 1. Sergey Balashevich Sr. Software Engineer @ Altoros Technical Introduction to Fabric an IBM’s contribution to May 5, 2016 Boston, MA
- 2. What is the Blockchain?
- 3. 3
- 4. BlockchainBlockchain BitcoinBitcoin HyperledgerHyperledger IBM FabricIBM Fabric EthereumEthereum C++, Go, Java, Python, Ruby, Javascript, Haskell bkirwi & jamshidh, Node, .NET C++, Go, Java, Python, Ruby, Javascript, Haskell bkirwi & jamshidh, Node, .NET
- 6. Not one but many…. A world of many networks
- 8. What is scope of core Hyperledger vs non-core?
- 10. 10
- 11. 11
- 12. 12 Step4: Deploy application 13 VP 1 VM VP 3 VM APP VP 2 VM CLI Chaincode
- 13. 13 Application is distributed across all peers 15 VP 1 VM APP VP 3 VM APP VP 2 VM APP CLI App source
- 14. 14 Transaction flow 19 CLI PEER CHAINCODE LEDGER OTHER PEER CHAINCODE_NEW
- 15. 15 Transaction flow 20 CLI PEER CHAINCODE LEDGER OTHER PEERStart transaction
- 16. 16 Transaction flow 21 CLI PEER CHAINCODE LEDGER OTHER PEERSet empty state
- 17. 17 Transaction flow 22 CLI PEER CHAINCODE LEDGER OTHER PEERExecute chaincode
- 18. 18 Transaction flow 23 CLI PEER CHAINCODE LEDGER OTHER PEER Apply state changes
- 19. 19 Transaction flow 24 CLI PEER CHAINCODE LEDGER OTHER PEERCommit transaction
- 20. 20 Transaction flow 25 CLI PEER CHAINCODE LEDGER OTHER PEER Broadcast transaction
- 21. 21 Consensus: System properties 27 The algorithm provides both safety and liveness assuming no more than 1/3 replicas are faulty.
- 22. 22 Consensus: Practical Byzantine Fault Tolerance 28
- 23. Hyperledger Roadmap Enterprise Integration Performance and Scalability Additional Consensus Plugins Additional Languages Portability
Editor's Notes
- all transactions are open. there are pros and cons
- Increasing demand for permissioned networks Some users/use cases require validating or non-validating nodes to be controlled or sometimes just sponsored by select whitelisted organizations Many network operators want transactors on network to obtain an identity from an issuing authority service on the network Need for private networks, as well as public networks Privacy on iPhone…. Privacy on the network? Many network operators want to keep identity and patterns of behavior completely private, inaccessible for 3rd parties 6. Performance / Scalability 7. World of many networks...
- goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.