Posted: 17 Aug 2017 9:08 EDT Last activity: 13 Oct 2017 8:58 EDT
Why Pega is deployed to Pivotal Cloud Foundry as a service
Based on the provided instructions, Pega deployed in PCF as a service. I would like to understand what is the rationale of the architecture. By deploying it as a service it does not use the benefits of PCF Elastic runtime, in particular ability to dynamically allocate resources.
Elastime Runtime, while powerful running certain type of applications, it imposes some limitations deploying Distributed Systems. Pega Platform is a distributed system. We worked with Pivotal and we agreed an On-Demand Service Broker is the best way to deploy Pega pn PCF.
The solution seems to me misses the main benefit of cloud, the on-demand provision of computing resources. I do not see much difference of Pega on PCF and deployment on traditional infrastructure as i still need to allocate VMs at deployment time.
What are these limitations that prevent from deploying Pega as an application, not a service?