Ordering Service
The ordering service package transactions into blocks to be delivered to peers.
Communication with the service is via channels.
Different configuration options for the ordering service include :
- SOLO
- Kafka : Crash fault tolerant consensusThe ordering service package transactions into blocks to be delivered to peers.
Communication with the service is via channels.
Different configuration options for the ordering service include :
- SOLO
- Single node for development
- 3 nodes minimum
- Odd number of nodes recommended
Channels provide privacy between different ledgers
- Ledgers exist in the scope of a channel
- Channels can be shared across an entire network of peers
- Channels can be permissioned for a specific set of participants
- Chaincode is instantiated on specific channels
- Peers can participate in multiple channels
- Concurrent execution for performance and scalability
Single Channel Network
- All peers connect to the same system channel (blue).
- All peers have the same chaincode and maintain the same ledger
- Endorsement by peers E0,E1,E2 and E3
Multi-Channel Network
- Peers E0 and E3 connect to the red channel for chaincodes Y and Z
- Peers E1 and E2 connect to the blue channel for chaincodes A and B
Fabric Peer
- Each peer :
- Connects to one or more channels
- Maintain one or more ledger for each channel
- Chaincodes are instantiated in separate docker containers
- Chaincodes are shared across channels (no state is stored in chaincode container)
- Local MSP (Membership Service Provider) provides crypto material
- Emits events to the client application
Client Apllication
Each client application uses Fabric SDK to :
Fabric Certificate Authority
No comments:
Post a Comment