Please enable JavaScript.
Coggle requires JavaScript to display documents.
Blockchain (Hyperledger (Linux Foundation (Big data and analytics: ODPi, R…
Blockchain
Hyperledger
-
-
-
Linux Foundation
Big data and analytics: ODPi, R Consortium
Networking: OpenDaylight, OPNFV
Embedded: Dronecode, Zephyr
Web tools: JS Foundation, Node.js
Cloud computing: Cloud Foundry, Cloud Native Computing Foundation, Open Container Initiative
-
-
-
-
-
-
Ordering mechanisms
Kafka is the Hyperledger Fabric ordering mechanism that is recommended for production use. This ordering mechanism utilizes Apache Kafka, an open source stream processing platform that provides a unified, high-throughput, low-latency platform for handling real-time data feeds. In this case, the data consists of endorsed transactions and RW sets. The Kafka mechanism provides a crash fault-tolerant solution to ordering.
-
SOLO is the Hyperledger Fabric ordering mechanism most typically used by developers experimenting with Hyperledger Fabric networks. SOLO involves a single ordering node.
SBFT stands for Simplified Byzantine Fault Tolerance. This ordering mechanism is both crash fault-tolerant and byzantine fault-tolerant, meaning that it can reach agreement even in the presence of malicious or faulty nodes. The Hyperledger Fabric community has not yet implemented this mechanism, but it is on their roadmap.
World State
Database State
Default: LevelDB
the default key/value state database for Hyperledger Fabric, and simply stores key/value pairs.
Substitution: CouchDB
an alternative to LevelDB. Unlike LevelDB, CouchDB stores JSON objects. CouchDB is unique in that it supports keyed, composite, key range, and full data-rich queries.
-
-
-
-
Chain code
-
Type of chain code
-
-
(More efficient way) Use chaincode to create decentralized applications that manage the lifecycle of one or multiple types of business contracts, and let the end users instantiate instances of contracts within these applications.
-
Requirements
-
-
As a developer, you must create both an Init and an Invoke method within your chaincode.
The chaincode must be installed using the peer chaincode install
command,
and instantiated using the peer chaincode instantiate
command before the chaincode can be invoked.
Then, transactions can be created using the peer chaincode invoke
or peer chaincode query
commands.
As such, the fabric peer has a --peer-chaincodedev
flag that can be passed on start-up to instruct the peer node not to deploy the chaincode as a Docker container.
You will need multiple terminal windows - essentially one for each component. One runs the validating peer; another runs the chaincode; the third runs the CLI or REST API commands to execute transactions. Finally, when running with security enabled, an additional fourth window is required to run the Certificate Authority (CA) server. Detailed instructions are provided in the sections below.
Finishing up
Remove all Docker containers and images that we created in this tutorial with the following command in the tuna-app folder:
-
-
-
-
-
-
-
-
-