안녕하세요, 급 만들어보고 싶은 어플리케이션이 생겨서 공부도 할 겸 정리해봅니다 :)
Amazon Managed Blockchain is a fully managed service for creating and managing blockchain networks and network resources using open-source frameworks.
What Amazon does for us?
- Scale to meet the demands of thousands of applications running milions of transactions.
- Simplify the management of blockchain networks and resources
- Manage certificates, let us easily create proposals for a vote among network members.
- Easily track operational metrics related to requests, computational load, memory usage, and data storage.
🤔... Anyway networks and resources are all managed by Amazon, it makes me think of 'is it actually decentralized?'
Networks, Members, and Peer Nodes
A blockchain network is a peer-to-peer network running a decentralized blockchain framework.
Member 👩:
- An unique identity in the network. i.g an organization in a consortium of banks.
Peer Nodes 🟠 : - Each member runs one or more Hyperledger Fabric peer nodes. The peer nodes run chaincode, endorse transactions, and store a local copy of ledger.
Amazon Managed Blockchain creates and manages these components (including Hyperledger Fabric ordering service and network configuration) for each member in a network.
A network on Managed Blockchain remains active as long as there are members. The network is deleted only when the last member deletes itself from the network.
The below image shows the basic components of a blockchain running.
The network creator defines a voting policy for the network during creation. The voting policy determines the basic rules for all proposal voting on the network.
When a new peer node in a channel comes online, it fetches the global state and ledger from other peers. Even if there are no other peer nodes on a network, as long as a member exists, ledger data can be restored to a new peer node. (How? Does Amazon store the global state somewhere?)
How to identify each other's peer nodes?
When a network is created, Managed Blockchain gives unique IDs to resources.
Each network resource has a unique, addressable endpoint that Managed Blockchain creates from these IDs.
Resource endpoints for a Hyperledger Fabric network on Managed Blockchain are in the following format:
ResourceID.MemberID.NetworkID.managedblockchain.AWSRegion.amazonaws.com:PortNumber
Within the Hyperledger Fabric network, access and authorization for each resource is governed by processes defined in the chaincoide and network configurations.
Managed Blockchain uses AWS PrivateLink to ensure that only network members can access required resources.
Ref: Key Concepts: Amazon Managed Blockchain Networks, Members, and Peer Nodes
