![Pivotal Cloud Foundry vs. webMethods AgileApps Cloud [EOL] report](https://www.peerspot.com/assets/media/images/icons/pdf-80836ec5.svg){kind=icon}
![webMethods AgileApps Cloud [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_64/vq7ys73l37mum8l959ajpau84w82.jpg?_a=BACAGSDL)
![webMethods AgileApps Cloud [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_30/vq7ys73l37mum8l959ajpau84w82.jpg?_a=BACAGSDL){kind=small}
![webMethods AgileApps Cloud [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_40/vq7ys73l37mum8l959ajpau84w82.jpg?_a=BACAGSDL){kind=small}
Regarding the setup phase, every step is a hurdle. With Pivotal Cloud Foundry, I won't get any proper resources for that. Even if I Google it, there is no proper solution for Pivotal Cloud Foundry. However, if we go for Azure or some other cloud, we can get a lot of information. I believe there is not much information for Pivotal Cloud Foundry since it may be some license issue. If you go for Azure, the migration process is straightforward. Since we have been given 10 GB of space in the public cloud, we are utilizing it in our company. So, we are trying to deploy our application on the cloud, and for us, it is like a trial process for now. From our total application rate, I can say that only two to three percent is on Pivotal Cloud Foundry. Currently, half of the code is in the shell script, which is causing issues. Also, most people in my organization have worked on Java-related code. For most of the applications, they are using the same, that is, shell script and AUTOsist, and so we haven't migrated yet. So that is the reason that we are planning to opt for a hybrid model so that we don't have to migrate completely to Pivotal Cloud Foundry.
