Consider the idea of running the Hyperledger node as an application in Cloud Foundry. Though you can create a build pack with Go, RocksDB, executable files for Docker, there are several challenges in this configuration.
In addition to the “peer” application, the Docker demon should also be started inside the CF container.
The CF application exposes just 1 network port by default. So, we cannot start a REST endpoint in the same container where the validation peer is started.
Workaround - we can run “Membership service”, “Validation peer” and “REST client” as different applications in CF using -c option at application deploy time.
CF Router supports only a limited number of protocols/ On the application level, there is a problem with Enrolment Certificate (it can be issued just once), in case if CF restarts your application - Validation Peer will not be able to apply for another Enrolment certificate using the same credentials. Workaround - It possible to save Certificates in external persistent storage and load them at the start time. In any case, VP will have just 1 instance in CF (scalability will not be used)
As a result, we can hardly use such CF benefits like scalability and automatic failover without customizing to the Fabric core.