When provisioning an instance of OBCS, you can choose what kind of ordering (orderer) service you want to use. In version one of OBCS, you can choice between SOLO and Kafka. SOLO is mainly used for development and provides a single process, whereas Kafka performs the serialization of transactions and ensures high availability. When using vanilla Fabric 1.0, the Kafka cluster must set the retention period to infinity as it is the single source of truth and an essential part of keeping data integrity.
Oracle developed some enhancements for their orderer node. In OBCS, the orderer node uses the Event Hub Cloud Service (EHCS) as its managed Apache Kafka instance. It's maximum retention time is two weeks. So, instead of keeping ...
