问题描述
除了Composer使原型业务网络的部署和测试变得更加容易的事实，以及我们不必知道golang来开发链码的事实之外，这些接口所提供的功能上的差异是什么?选择一个而不是另一个?
Other than the fact that Composer makes deployment and testing of prototype business networks easier and the fact that we don't have to know golang to develop chaincode, what is the difference in the functionalities that these interfaces provide that may lead one to choose one over the other?
推荐答案
本文可能会为您提供所需的答案:
This article can probably provide you with the answers you need:
https://blog.selman. org/2017/07/08/getting-started-with-blockchain-development/
Hyperledger Composer既是应用程序开发框架，又是一组功能强大的工具，可简化和加快最终在Hyperledger Fabric区块链上执行的区块链应用程序和智能合约的创建. Composer有其自己的运行时，即通用链码，并托管和解释所部署的业务网络-因此，您的智能合约仅需使用Javascript，而无需使用您提到的Go a(Fabric的域)中的链码.它还具有建模工具，可用于创建您的业务网络模型并定义诸如访问控制列表和要执行的查询之类的控件.
Hyperledger Composer is both an application development framework and set of powerful tools which simplifies and expedites the creation of blockchain applications and smart contracts that are ultimately executed on the Hyperledger Fabric blockchain. Composer has its own runtime, that is generic chaincode and hosts and interprets the business network deployed - so your smart contract need only use Javascript, not chaincode in Go a (which is Fabric's domain) s you mentioned. It also has a modeling facility to create your business network model and to define such controls as Access Control lists and queries to be executed.
此体系结构链接应帮助您进一步理解-> https://www. slideshare.net/SimonStone8/hyperledger-composer-architecture
This architecture link should help you with further understanding -> https://www.slideshare.net/SimonStone8/hyperledger-composer-architecture
此外，请参阅Hyperledger Composer文档，请参见此处:
Furthermore see the Hyperledger Composer docs, see here:
https://hyperledger.github.io/composer/
要查看Hyperledger Fabric文档-参见此处:
TO see the Hyperledger Fabric docs - see here:
https://hyperledger-fabric.readthedocs.io/en/latest/
这篇关于Fabric Javascript SDK和Hyperledger Composer之间的功能区别是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！