Original title: "Hyperledger Fabric and enterprise ethereum, which is the preferred enterprise?"
Block chain headquarters
Over the past year, we've seen a lot of interest in enterprise-class blockchain platforms or distributed ledger technology (DLT). Due to privacy, regulatory, and scalability concerns, companies tend to use privately licensed ledgies rather than the currently available public mains. As a result, we see two projects that are very attractive -- Enterprise Ethereum and Hyperledger Fabric. In this article, we will explore and compare them. & have spent
Enterprise ethereum
Enterprise ethereum is a private consortium implementation of the ethereum codex. It is primarily driven by the enterprise ethereum alliance, whose primary goal is to address enterprise needs and strive for interoperability while evolving around the public ethereum blockchain. & have spent 1) community enterprise-level ethereum benefits from the world's largest blockchain development community. Thousands of software engineers, product developers, and designers are working in the ecosystem to build the infrastructure, development tools, and applications. Many organizations and governments report that they are deploying enterprise ethereum into their workflows. & have spent
Hyperledger Fabric
Hyperledger Fabric (HLF), part of the Hyperledger Greenhouse, is an enterprise-class distributed ledger technology that supports privacy and allows for a wide range of plug-and-play capabilities (consensus algorithms, components, member management services, and so on). Because of its modular and generic design, the technology satisfies a large number of use cases for businesses and industries (supply chains, healthcare). 1) the Fabric community is steadily growing, with more than 20,000 users in its chat, problem tracking, and roadmap. 2) deployment because of its unique approach to distributed ledger technology, which enables large-scale solutions, Hyperledger Fabric (HLF) is primarily used in enterprises.
The client
Let's look at the different software clients that can be used to run enterprise-class distributed ledgers. On evm-based networks, we have Hyperledger Besu and Quorum. Hyperledger Fabric, on the other hand, has only one implementation. It does not have a similar EVM chain-based client. When we refer to the Hyperledger Fabric client, we are referring to the only implementation organized by the Linux foundation.
For clarity, Hyperledger itself is a large project of the Linux foundation. Hyperledger has a suite of open source blockchain projects and development tools. One of the blockchain projects is Hyperledger Fabric, and the other is Hyperledger Besu (an enterprise-class ethereum client previously developed by consensus and called Pantheon). & have spent Hyperledger Besu is a java-based evm-based blockchain client with other "enterprise-friendly" features.
2) Quorum Quorum is an evm-based client developed primarily by JP Morgan. It is a fork (written in Go) from the Geth client. This is the first enterprise-centric ethereum client with enhanced privacy capabilities.
Enterprise blockchain platform comparison

We can see that both Quorum and Besu have very similar specifications and, of course, both are customers of enterprise ethereum, but we can mention the following:
Besu has a more advanced JSON RPC API license. The client supports JWT authentication, which can be used to define the access rights of the bearer, from which RPC can be invoked, and so on. In its latest release (1.4.2), the team added more tenant based features.
Quorum has a more advanced on-chain license. We can use its predefined API calls and contracts to define organizations, suborganizations, administrators, and so on.
Who provides BaaS?
& have spent As the space matures, we see more and more cloud providers offering BaaS solutions. The biggest, of course, is the AWS managed blockchain. AWS currently offers HLF as a service, and ethereum as a service is in its planning. IBM blockchain -- IBM also offers HLF as a service. Azure blockchain - Azure provides the deployment of the Quorum/Geth network and the blockchain development suite.
Other cloud providers are joining BaaS. LimeChain has consulted and helped iNNOVO Cloud offer its own blockchain solution and enter the market.
The future of enterprise-class blockchain platform & NBSP;
In recent months, we've seen a lot of companies using the blockchain platform. And for the past two or three years, the main focus of these companies has been on producing proof of concept (PoC) and figuring out how blockchain can help in its workflow or process. The licensed blockchain network has changed, and it does not seem efficient to deploy the blockchain network for each member of the alliance.
If we take this approach, at some point, companies will be required to join many alliances in order to do business with other companies. This is not about using technology to reduce costs, but to increase them due to complexity. For example, an open source project called Baseline, a recently released open source project, attempts to use public Mainnet (ethereum) as a common reference framework. The idea of deploying a licensed network for an alliance has shifted to making use of a Shared or common infrastructure known as Mainnet, the benchmark protocol used for "state" clearing over a global Shared infrastructure (the main network).

conclusion
Enterprise-class blockchain platforms are becoming more sophisticated and can be used in production. A year or two ago, developers and administrators had to build their apis or license schemes on the chain, and now they can be provided as features of the client itself. However, choosing the right enterprise-class blockchain platform for your business is not easy, and may be suitable for your solution or different from existing solutions. Companies that form large alliances tend to use the Hyperledger Fabric network. On the other hand, we have some use cases where the Hyperledger Fabric network is only used for internal processes without any external organization. It is often more expensive to deploy, configure, and maintain a Hyperledger Fabric network than to deploy an evm-based network, which is why we see smaller projects using enterprise ethereum instead of Hyperledger Fabric. & have spent
New protocols are emerging that reduce the currently isolated enterprise structure by using the public ethereum master network as a common frame of reference. This provides the ability to avoid problems caused by the alliance deploying licensed networks. Over the next few months, we should see concrete examples of this design pattern in action, and the question of whether the enterprise is willing to adopt it will be answered.
The original address: https://mp.weixin.qq.com/s/FZd6EguDIarbKO0ZmBedjA
Welcome to join the official BlockBeats community:
Telegram Subscription Group: https://t.me/theblockbeats
Telegram Discussion Group: https://t.me/BlockBeats_App
Official Twitter Account: https://twitter.com/BlockBeatsAsia