Note: This review is written while closing very small projects with Hyperledger Fabric(henceforth HLF).
You can easily find articles regarding pros and cons of HLF network architecture - ex. consensus algorithm, permission and so one - comparing with others - ex. Bitcoin, ethereum. So, in this articile, I would like to discuss things in a point of developing Chaincode.
Updating same state at multiple transactions
I think most important and biggest difference in terms of developing Chaincode between HLF and other popular networks, is
In case that several transactions try to update same global state, only one transaction is allowed in a block!
This comes from architectural design of HLF - Orderer(I think this is a kind of debt for hight TPS). Even if time interval of creating block, is very short comaring with other networks, this is very serious constraints. For example, in case of money trading system, only one transfer-transaction is allowed in a block for same account. Because of this characteristics - high TPS with contraints described above, HLF is very good for assets having it's own ID like house, products and so one. But, it's not good for assets requiring couting and calculation like money.
To overcome this constraints, HLF suggests sample codes at their <fabric-sample>/high-troughput. But I think this is not enough. For example, to know current balance, transaction have to read all accumulated variables. And to transfer money, one variable is added to global state. That is, still only one transaction is allowed in a block because read-set to calculate current balance is updated(added)!
I think followings are not HLF specific issues. But to me, these are also annoying. And I can't find any good way to reduce these pain points at SDKs or libraries for Chaincode.
- Read/Write operation on global state is very expensive. And reading variable that is updated in same transaction gives it's original value(not updated value)
- ECDSA is algorithm for digital signature, not for en/decryption.
- Testing Chaincode requires HLF networks. So, test and debugging cycle takes longer time than expected.
I hope that HLF team provides good solutions for them. And until then, I hope my sample template - hlfcc-node-starter - is helpful to other developers using typscript as their Chaincode-language.
'Domain > Blockchain-DLT' 카테고리의 다른 글
|[HLF] Things to know to build your first network with docker-compose. (0)||2019.05.03|
|[DLT][HLF] Distribute(Release) NodeJs Chaincode (0)||2019.05.03|
|[DLT][HLF] Structure of ‘msp’ directory generated by ‘cryptogen’ tool (0)||2019.05.03|
|[DLT] Review: Hyperledger Fabric (v1.2.x) (0)||2019.05.03|