mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-10 22:21:11 +08:00
TSL
This commit is contained in:
Xingyu Wang
parent
9dfff30415
commit
c19320c06c
@ -1,81 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (wxy)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Blockchain 2.0 – Introduction To Hyperledger Fabric [Part 10])
|
||||
[#]: via: (https://www.ostechnix.com/blockchain-2-0-introduction-to-hyperledger-fabric/)
|
||||
[#]: author: (sk https://www.ostechnix.com/author/sk/)
|
||||
|
||||
Blockchain 2.0 – Introduction To Hyperledger Fabric [Part 10]
|
||||
======
|
||||
|
||||
![Hyperledger Fabric][1]
|
||||
|
||||
### Hyperledger Fabric
|
||||
|
||||
The [**Hyperledger project**][2] is an umbrella organization of sorts featuring many different modules and systems under development. Among the most popular among these individual sub-projects is the **Hyperledger Fabric**. This post will explore the features that would make the Fabric almost indispensable in the near future once blockchain systems start proliferating into main stream use. Towards the end we will also take a quick look at what developers and enthusiasts need to know regarding the technicalities of the Hyperledger Fabric.
|
||||
|
||||
### Inception
|
||||
|
||||
In the usual fashion for the Hyperledger project, Fabric was “donated” to the organization by one of its core members, **IBM** , who was previously the principle developer of the same. The technology platform shared by IBM was put to joint development at the Hyperledger project with contributions from over a 100 member companies and institutions.
|
||||
|
||||
Currently running on **v1.4** of the LTS version, Fabric has come a long way and is currently seen as the go to enterprise solution for managing business data. The core vision that surrounds the Hyperledger project inevitably permeates into the Fabric as well. The Hyperledger Fabric system carries forward all the enterprise ready and scalable features that are hard coded into all projects under the Hyperledger organization.
|
||||
|
||||
### Highlights Of Hyperledger Fabric
|
||||
|
||||
Hyperledger Fabric offers a wide variety of features and standards that are built around the mission of supporting fast development and modular architectures. Furthermore, compared to its competitors (primarily **Ripple** and [**Ethereum**][3]), Fabric takes an explicit stance toward closed and [**permissioned blockchains**][4]. Their core objective here is to develop a set of tools which will aid blockchain developers in creating customized solutions and not to create a standalone ecosystem or a product.
|
||||
|
||||
Some of the highlights of the Hyperledger Fabric are given below:
|
||||
|
||||
* **Permissioned blockchain systems**
|
||||
|
||||
|
||||
|
||||
This is a category where other platforms such as Ethereum and Ripple differ quite a lot with Hyperledger Fabric. The Fabric by default is a tool designed to implement a private permissioned blockchain. Such blockchains cannot be accessed by everyone and the nodes working to offer consensus or to verify transactions are chosen by a central authority. This might be important for some applications such as banking and insurance, where transactions have to be verified by the central authority rather than participants.
|
||||
|
||||
* **Confidential and controlled information flow**
|
||||
|
||||
|
||||
|
||||
The Fabric has built in permission systems that will restrict information flow within a specific group or certain individuals as the case may be. Unlike a public blockchain where anyone and everyone who runs a node will have a copy and selective access to data stored in the blockchain, the admin of the system can choose how to and who to share access to the information. There are also subsystems which will encrypt the stored data at better security standards compared to existing competition.
|
||||
|
||||
* **Plug and play architecture**
|
||||
|
||||
|
||||
|
||||
Hyperledger Fabric has a plug and play type architecture. Individual components of the system may be chosen to be implemented and components of the system that developers don’t see a use for maybe discarded. The Fabric takes a highly modular and customizable route to development rather than a one size fits all approach taken by its competitors. This is especially attractive for firms and companies looking to build a lean system fast. This combined with the interoperability of the Fabric with other Hyperledger components implies that developers and designers now have access to a diverse set of standardized tools instead of having to pull code from different sources and integrate them afterwards. It also presents a rather fail-safe way to build robust modular systems.
|
||||
|
||||
* **Smart contracts and chaincode**
|
||||
|
||||
|
||||
|
||||
A distributed application running on a blockchain is called a [**Smart contract**][5]. While the smart contract term is more or less associated with the Ethereum platform, chaincode is the name given to the same in the Hyperledger camp. Apart from possessing all the benefits of **DApps** being present in chaincode applications, what sets Hyperledger apart is the fact that the code for the same may be written in multiple high-level programming language. It supports [**Go**][6] and **JavaScript** out of the box and supports many other after integration with appropriate compiler modules as well. Though this fact might not mean much at this point, the fact remains that if existing talent can be used for ongoing projects involving blockchain that has the potential to save companies billions of dollars in personnel training and management in the long run. Developers can code in languages they’re comfortable in to start building applications on the Hyperledger Fabric and need not learn nor train in platform specific languages and syntax. This presents flexibility which current competitors of the Hyperledger Fabric do not offer.
|
||||
|
||||
* The Hyperledger Fabric is a back-end driver platform and is mainly aimed at integration projects where a blockchain or another distributed ledger technology is required. As such it does not provide any user facing services except for minor scripting capabilities. (Think of it to be more like a scripting language.)
|
||||
* Hyperledger Fabric supports building sidechains for specific use-cases. In case, the developer wishes to isolate a set of users or participants to a specific part or functionality of the application, they may do so by implementing side-chains. Side-chains are blockchains that derive from a main parent, but form a different chain after their initial block. This block which gives rise to the new chain will stay immune to further changes in the new chain and the new chain remains immutable even if new information is added to the original chain. This functionality will aid in scaling the platform being developed and usher in user specific and case specific processing capabilities.
|
||||
* The previous feature also means that not all users will have an “exact” copy of all the data in the blockchain as is expected usually from public chains. Participating nodes will have a copy of data that is only relevant to them. For instance, consider an application similar to PayTM in India. The app has wallet functionality as well as an e-commerce end. However, not all its wallet users use PayTM to shop online. In this scenario, only active shoppers will have the corresponding chain of transactions on the PayTM e-commerce site, whereas the wallet users will just have a copy of the chain that stores wallet transactions. This flexible architecture for data storage and retrieval is important while scaling, since massive singular blockchains have been shown to increase lead times for processing transactions. The chain can be kept lean and well categorised this way.
|
||||
|
||||
|
||||
|
||||
We will look at other modules under the Hyperledger Project in detail in upcoming posts.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.ostechnix.com/blockchain-2-0-introduction-to-hyperledger-fabric/
|
||||
|
||||
作者：[sk][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.ostechnix.com/author/sk/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7
|
||||
[2]: https://www.ostechnix.com/blockchain-2-0-an-introduction-to-hyperledger-project-hlp/
|
||||
[3]: https://www.ostechnix.com/blockchain-2-0-what-is-ethereum/
|
||||
[4]: https://www.ostechnix.com/blockchain-2-0-public-vs-private-blockchain-comparison/
|
||||
[5]: https://www.ostechnix.com/blockchain-2-0-explaining-smart-contracts-and-its-types/
|
||||
[6]: https://www.ostechnix.com/install-go-language-linux/
|
||||
@ -0,0 +1,73 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (wxy)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Blockchain 2.0 – Introduction To Hyperledger Fabric [Part 10])
|
||||
[#]: via: (https://www.ostechnix.com/blockchain-2-0-introduction-to-hyperledger-fabric/)
|
||||
[#]: author: (sk https://www.ostechnix.com/author/sk/)
|
||||
|
||||
区块链 2.0：Hyperledger Fabric 介绍（十）
|
||||
======
|
||||
|
||||
![Hyperledger Fabric][1]
|
||||
|
||||
### Hyperledger Fabric
|
||||
|
||||
[Hyperledger 项目][2] 是一个伞形组织，具有许多正在开发的不同模块和系统。在这些子项目中，最受欢迎的是 “Hyperledger Fabric”。这篇博文将探讨一旦区块链系统开始大量使用到主流，将使 Fabric 在不久的将来几乎不可或缺的功能。最后，我们还将快速了解开发人员和爱好者们需要了解的有关 Hyperledger Fabric 技术的知识。
|
||||
|
||||
### 起始时间
|
||||
|
||||
按照 Hyperledger 项目的常规方式，Fabric 由其核心成员之一 IBM “捐赠”给该组织，而 IBM 以前是该组织的主要开发者。IBM 共享的这个技术平台在 Hyperledger 项目中进行了联合开发，来自 100 多个成员公司和机构为之做出了贡献。
|
||||
|
||||
目前，Fabric 正处于 LTS 版本的 v1.4，该版本已经发展很长一段路，并且被视为企业管理业务数据的解决方案。Hyperledger 项目的核心愿景也不可避免地渗透到了 Fabric 中。Hyperledger Fabric 系统继承了所有企业级的可扩展功能，这些功能已深深地刻入到 Hyperledger 组织下的所有项目中。
|
||||
|
||||
### Hyperledger Fabric 的亮点
|
||||
|
||||
Hyperledger Fabric 提供了多种功能和标准，这些功能和标准围绕支持快速开发和模块化体系结构的使命而构建。此外，与竞争对手（主要是瑞波和[以太坊][3]）相比，Fabric 对封闭和[许可区块链][4]采取了明确的立场。它们的核心目标是开发一套工具，这些工具将帮助区块链开发人员创建定制的解决方案，而不是创建独立的生态系统或产品。
|
||||
|
||||
Hyperledger Fabric 的一些亮点如下：
|
||||
|
||||
#### 许可区块链系统
|
||||
|
||||
这是一个 Hyperledger Fabric 与其他平台（如以太坊和瑞波）差异很大的类别。默认情况下，Fabric 是一种旨在实现私有许可的区块链的工具。此类区块链不能被任何人访问，并且致力于达成共识或验证交易的节点由中央机构选择。这对于某些应用（例如银行和保险）可能很重要，在这些应用中，交易必须由中央机构而不是参与者来验证。
|
||||
|
||||
#### 机密和受控的信息流
|
||||
|
||||
Fabric 内置了权限系统，该权限系统将视情况限制特定组或某些个人中的信息流。与公有区块链不同，在公有区块链中，任何运行节点的人都可以对存储在区块链中的数据进行复制和选择性访问，而 Fabric 系统的管理员可以选择谁能访问共享信息，以及访问的方式。与现有竞争产品相比，它还有以更好的安全性标准对存储的数据进行加密的子系统。
|
||||
|
||||
#### 即插即用架构
|
||||
|
||||
Hyperledger Fabric 具有即插即用类型的体系结构。可以选择实施系统的各个组件，而开发人员看不到用处的系统组件可能会被废弃。Fabric 采取高度模块化和可定制的方式进行开发，而不是一种与其竞争对手采用的一种方法适应所有需求的方式。对于希望快速构建精益系统的公司和公司而言，这尤其有吸引力。这与 Fabric 与其它 Hyperledger 组件的互操作性相结合，意味着开发人员和设计人员现在可以使用各种标准化工具，而不必从其他来源提取代码并随后进行集成。 它还提供了一种相当可靠的方式来构建健壮的模块化系统。
|
||||
|
||||
#### 智能合约和链码
|
||||
|
||||
运行在区块链上的分布式应用程序称为[智能合约][5]。虽然智能合约这个术语或多或少与以太坊平台相关联，但<ruby>链码<rt>chaincode</rt></ruby>是在 Hyperledger 阵营中为其赋予的名称。链码应用程序除了拥有 DApps 中存在的所有优点之外，使 Hyperledger 与众不同的是，该应用程序的代码可以用多种高级编程语言编写。它本身支持 [Go][6] 和 JavaScript，并且在与适当的编译器模块集成后还支持许多其他语言。尽管这一事实在此时可能并不意味着什么，但这意味着，如果可以将现有人才用于正在进行的涉及区块链的项目，从长远来看，这有可能为公司节省数十亿美元的人员培训和管理费用。开发人员可以使用自己喜欢的语言进行编码，从而在 Hyperledger Fabric 上开始构建应用程序，而无需学习或培训平台特定的语言和语法。这提供了 Hyperledger Fabric 当前竞争对手无法提供的灵活性。
|
||||
|
||||
### 总结
|
||||
|
||||
* Hyperledger Fabric 是一个后端驱动程序平台，是一个主要针对需要区块链或其它分布式账本技术的集成项目。因此，除了次要的脚本功能外，它不提供任何面向用户的服务。（认可以为它更像是一种脚本语言。）
|
||||
* Hyperledger Fabric 支持针对特定用例构建侧链。如果开发人员希望将一组用户或参与者隔离到应用程序的特定部分或功能，则可以通过侧链来实现。侧链是衍生自主要父代的区块链，但在其初始块之后形成不同的链。产生新链的块将不受新链进一步变化的影响，即使将新信息添加到原始链中，新链也将保持不变。此功能将有助于扩展正在开发的平台，并引入用户特定和案例特定的处理功能。
|
||||
* 先前的功能还意味着并非所有用户都会像通常对公有链所期望的那样拥有区块链中所有数据的“精确”副本。参与节点将具有仅与之相关的数据副本。例如，假设一个类似于印度的 PayTM 的应用程序。该应用程序具有钱包功能以及电子商务功能。但是，并非所有的钱包用户都使用 PayTM 在线购物。在这种情况下，只有活跃的购物者将在 PayTM 电子商务网站上拥有相应的交易链，而钱包用户将仅拥有存储钱包交易的链的副本。这种灵活的数据存储和检索体系结构在扩展时非常重要，因为大量的单链区块链已经显示出会增加处理交易的前置时间。这样可以保持链的精简和分类。
|
||||
|
||||
我们将在以后的文章中详细介绍 Hyperledger Project 下的其他模块。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.ostechnix.com/blockchain-2-0-introduction-to-hyperledger-fabric/
|
||||
|
||||
作者：[sk][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[wxy](https://github.com/wxy)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.ostechnix.com/author/sk/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7
|
||||
[2]: https://www.ostechnix.com/blockchain-2-0-an-introduction-to-hyperledger-project-hlp/
|
||||
[3]: https://www.ostechnix.com/blockchain-2-0-what-is-ethereum/
|
||||
[4]: https://www.ostechnix.com/blockchain-2-0-public-vs-private-blockchain-comparison/
|
||||
[5]: https://www.ostechnix.com/blockchain-2-0-explaining-smart-contracts-and-its-types/
|
||||
[6]: https://www.ostechnix.com/install-go-language-linux/
|
||||
Loading…
Reference in New Issue
Block a user