github.com/leonlxy/hyperledger@v1.0.0-alpha.0.20170427033203-34922035d248/docs/source/included.rst (about)

     1  What's Offered?
     2  ================
     3  
     4  The getting started example uses Docker images to generate the Fabric
     5  network components.  The scenario includes a consortium of three
     6  members, each managing and maintaing a peer node, as well as a "SOLO"
     7  :ref:`Ordering-Service` and a Certificate Authority (CA). The cryptographic identity
     8  material, based on standard PKI implementation, has been pre-generated
     9  and is used for signing + verification on both the server (peer + ordering service)
    10  and client (SDK) sides.  The CA is the network entity responsible for issuing
    11  and maintaing this identity material, which is necessary for authentication by all
    12  components and participants on the network.  This sample uses a single CA.  However,
    13  in enterprise scenarios each :ref:`Member` would likely have their own CA, with more
    14  complex security/identity measures implemented - e.g. cross-signing certificates, etc.
    15  
    16  The members will transact on a private channel, with a shared ledger maintained by
    17  each peer node.  Requests to read and write data to/from the ledger are sent
    18  as "proposals" to the peers.  These proposals are in fact a request for endorsement
    19  from the peer, which will execute the transaction and return a response to the
    20  submitting client.
    21  
    22  The sample demonstrates two methods for interacting with the network - a programmatical
    23  approach exercising the Node.js SDK APIs and a CLI requiring manual commands.
    24  
    25  It's recommended to follow the sample in the order laid forth - application first,
    26  followed by the optional CLI route.
    27  
    28  
    29