Fabric application model and architecture
In earlier chapters, we saw how Hyperledger Fabric can be viewed as a transaction processing system over a distributed database (corresponding to channel ledgers) maintained by the network peers, exposing information through a set of views. It is the developer's job to expose the assets and data items in the ledgers, as well as the transactions and queries on them, in a way that hides the complexity of the underlying network and channel architecture. In addition, the developer must provide differentiated capabilities to various enterprise users affiliated with the network's organizations, with appropriate security and privacy safeguards built in. Figure 9.2 illustrates what such a distributed Fabric application looks like:
Figure 9.2: Typical three-layer architecture of a Hyperledger Fabric application
As we can see, the Network layer at the bottom, consisting of network peers, ordering nodes, and CAs, is the infrastructure...
