organizations, with one peer each, an ordering service, the peer organization and ordering  service respective CAs and one channel. Figure 4-27 Example of business network and components This configuration is sufficient for two purposes: GLYPH<SM590000> Testing applications and smart contracts. GLYPH<SM590000> As a guide for building components and joining production networks that suit your needs. The network contains the following components: GLYPH<SM590000> Peer organizations : Organizations that need to transact with each other. Represented in  Figure 4-27 as Org 1 and Org 2.  GLYPH<SM590000> Ordering service organization : In a distributed ledger, the peers and ordering service  should be part of separate organizations. Therefore, a separate organization is created for  the ordering service. Among other things, an ordering service orders the blocks of  transactions that are sent to the peers to be written to their ledgers and become the  blockchain.  GLYPH<SM590000> Certificate authority (CA) : The node that issues certificates to both the users and the  nodes that are associated with an organization. It’s a best practice to deploy one CA per  organization. These CAs also create the definition of each organization, which is  encapsulated by a Membership Service Provider (MSP). A TLS CA is automatically  deployed together with each organization CA. The TSL CA provides the TLS certificates  that are used for communication between nodes. GLYPH<SM590000> Ordering service : Either a one-node ordering service or a crash fault tolerant five-node  ordering service. The ordering service uses an implementation of the Raft protocol, for  both one- and five-node configurations. One-node ordering service is suitable for  development and testing, while five-node ordering service provides crash fault-tolerance  174  Implementation Guide for IBM Blockchain Platform for Multicloud