Skip to content

Latest commit

 

History

History
48 lines (30 loc) · 5.35 KB

enterprise_plan.md

File metadata and controls

48 lines (30 loc) · 5.35 KB
copyright lastupdated
years
2017, 2018
2018-05-15

{:new_window: target="_blank"} {:shortdesc: .shortdesc} {:screen: .screen} {:codeblock: .codeblock} {:pre: .pre}

About Enterprise Plan

{{site.data.keyword.blockchainfull}} Platform Enterprise Plan is a production-ready offering for organizations who would like to create or join a blockchain network for real businesses. This plan provides the key infrastructure along with tools and support to easily start a highly secure and production-ready network. {:shortdesc}

Note: {{site.data.keyword.blockchainfull_notm}} Platform Enterprise Plan provides a production environment. If you need a development and testing environment, see About Starter Plan.

For members who are going to initiate the network, IBM provides a graphical user interface to guide the network initiator through key steps to set up and provision the network. This includes inviting other members and setting the governance rules. For more information, see Govern the Enterprise Plan network. After the network is deployed, an interactive graphical user interface, the Network Monitor, is available to monitor health and activity of the network; manage key network activities that include new deployments, members addition or removal, chaincode lifecycle, and channel management; and seek technical support. Find more information about the Network Monitor, see Operate the Enterprise Plan network.

Sign up now for your {{site.data.keyword.blockchainfull_notm}} membership External link icon.

The {{site.data.keyword.blockchainfull_notm}} Platform is built with key Hyperledger Fabric components that include a Certificate Authority (CA) and at least 1 peer (max of 6). Enterprise Plan also provides a crash fault tolerant (CFT) Kafka ordering service for the network members.

The Fabric CA is the certificate authority that is provided with the Enterprise plan. Two intermediate CAs are provided per member, which grant membership to the network. By using the CA, the member can also provide membership (certs) to users of the network.

It’s important to understand that for a transaction to be appended to the ledger, there are three phases that are involved:

  1. Transaction Simulation and Endorsement (peer)
  2. Ordering (ordering service)
  3. Validation and Commit (peer)

The Fabric peers owned by the members are the interface or gateway for applications to execute chain code, providing the business logic to execute transactions against the ledger. All transactions must be endorsed. The other members of the network do this endorsement. After endorsement, transactions are sent to an IBM provided ordering service (Kafka).

Besides the core blockchain components, the Enterprise Membership option provides an infrastructure with secure data storage and communications (TLS), and high availability. While Fabric networks share these infrastructure resources, isolation is provided for the Fabric component nodes in a network, and each node executes in a secure docker container that protects the execution environment.

The sole aspect that must be determined is the size of the peers that the network requires. This decision is based on the number of channels that are required, plus the workload per channel, memory usage, and disk space (storage).

You should use Enterprise Plan for more stable, production, or almost production level deployments. For testing purposes, use Starter Plan, develop in IBM Container Service, or install Docker images locally.

Pricing

To use the Enterprise plan, network members must pay $1,000 per month as the membership fee and additionally $1,000 per month for each of their peers in the network. The monthly fees are billed daily prorated. For example, a member (associated membership fee of $1,000) of two peers (per peer fee of $1,000 X 2 peers) needs to pay $3,000 every month. If the month has 30 days, the member pays $100 ($3,000/30) every day. Note that if you need high availability (HA), you must double your required peer numbers to provide the HA capabilities.

Network members can pay their bill with their own {{site.data.keyword.cloud_notm}} accounts that contain the space to create the network instance. Alternatively, one network member can cover the bill for all members in the network. For more information about how to pay for the blockchain networks, see Paying for the network.