Head of Engineering at a financial services firm with 10,001+ employees
Real User
Aug 23, 2023
One has to understand the scaling requirements for the application before you go to Pivotal. Then, YOU need to look at whether it's going to be on-premise or on AWS. We are PCF on AWS. Ideally, one should go through all the development and everything on AWS because you no longer have to have a set of infrastructure in your data center for it. You just delegate it to AWS PCF. Maybe right up to the user acceptance testing portion. Only production load; maybe you can just put it on-prem stuff. If there are some regulatory reasons and all that. But if you don't have any regulatory requirements, just go for PCF AWS. It would make your infrastructure management much easier. Overall, I would probably give it; comparing my OpenShift and AWS and all of that, I would probably give Pivotal Cloud Foundry a seven out of ten.
Our organization has been analyzing OpenShift and Pivotal Cloud Foundry. Regarding the comparison, there have been certain use cases, and I may not be the best person to tell you about them right now because my team is actually coming up with those use cases. So they were comparing Pivotal Cloud Foundry against what we are using and what is available in the market in OpenShift. We have considered Pivotal Cloud Foundry when moving our solutions to the cloud. We also follow the solution's design operational principles. As a private cloud, I recommend the solution to those planning to use it. We have been using it for quite a long time now, and I can say that it has no such stability-related issues. I rate the overall product a seven out of ten.
Assistant to Vice President at a consultancy with 10,001+ employees
Real User
Top 20
Mar 9, 2023
I give the solution a five out of ten. Some of our customers have moved away from Pivotal Cloud Foundry due to the risk of their apps not existing in a few years' time. Several of our larger customers in the US and Asia Pacific region have shifted to Red Hat OpenShift. I do not recommend Pivotal Cloud Foundry due to the uncertain nature of its future.
It's up-to-date, and it is a private cloud within the enterprise. It is hosted internally. I'd rate the solution seven out of ten based on the challenges we had surrounding migration. If a potential new user is new to the cloud and if they want to do an internal private cloud setup that is easy to deploy and push, I would recommend the new PCF.
My advice to others is to make sure Pivotal Cloud Foundry is the right solution for them. It could be the case where Microsoft Azure or Amazon AWS would be better. Pivotal Cloud Foundry
Senior Manager at a tech vendor with 10,001+ employees
Real User
Jul 29, 2022
My advice to others is they should evaluate Pivotal Cloud Foundry to see if it fits their needs. It's comparable to some of the better-known names. From an acceptance point of view, I think it has lower adoption, but people should explore this further. I rate Pivotal Cloud Foundry seven out of ten.
Owner/Full Stack Software Engineer at Maraphonic, Inc.
Real User
Top 10
May 11, 2022
What I saw recently was two big companies, trying to move from the PC to the cloud. They bought Pivotal Cloud Foundry and they are using it on a hybrid cloud. For example, they have two data centers and there are two installations of the Pivotal Cloud Foundry in each data center and they deploy microservices to each data center. They use external Amazon AWS to load balance. However, for some reason, the tendency right now for companies is to move to the Red Hat OpenShift, which is a commercial version of Kubernetes. I rate Pivotal Cloud Foundry a nine out of ten.
Sr. Cloud Architect at Intuitive Technology Partners
Real User
Top 10
Apr 28, 2020
When we are working with our clients, we start with gathering the requirements and then create a proof of concept. Because we are meeting the requirements, our clients do not complain about this solution. My advice for anybody who is implementing this solution is to first go through the documentation or do a hands-on lab to learn about the product. I would rate this solution a seven out of ten.
Pivotal Cloud Foundry (PCF) is the leading enterprise PaaS, powered by Cloud Foundry. PCF provides a cloud-native application platform that allows you to continuously deliver any app to every major private and public cloud with a single platform. PCF is proven to accelerate feature delivery with higher developer productivity and a 200:1 developer to operator ratio. PCF's built-in security and self-healing capabilities reduce risk in your app portfolio while maintaining high-availability...
One has to understand the scaling requirements for the application before you go to Pivotal. Then, YOU need to look at whether it's going to be on-premise or on AWS. We are PCF on AWS. Ideally, one should go through all the development and everything on AWS because you no longer have to have a set of infrastructure in your data center for it. You just delegate it to AWS PCF. Maybe right up to the user acceptance testing portion. Only production load; maybe you can just put it on-prem stuff. If there are some regulatory reasons and all that. But if you don't have any regulatory requirements, just go for PCF AWS. It would make your infrastructure management much easier. Overall, I would probably give it; comparing my OpenShift and AWS and all of that, I would probably give Pivotal Cloud Foundry a seven out of ten.
Our organization has been analyzing OpenShift and Pivotal Cloud Foundry. Regarding the comparison, there have been certain use cases, and I may not be the best person to tell you about them right now because my team is actually coming up with those use cases. So they were comparing Pivotal Cloud Foundry against what we are using and what is available in the market in OpenShift. We have considered Pivotal Cloud Foundry when moving our solutions to the cloud. We also follow the solution's design operational principles. As a private cloud, I recommend the solution to those planning to use it. We have been using it for quite a long time now, and I can say that it has no such stability-related issues. I rate the overall product a seven out of ten.
I give the solution a five out of ten. Some of our customers have moved away from Pivotal Cloud Foundry due to the risk of their apps not existing in a few years' time. Several of our larger customers in the US and Asia Pacific region have shifted to Red Hat OpenShift. I do not recommend Pivotal Cloud Foundry due to the uncertain nature of its future.
It's up-to-date, and it is a private cloud within the enterprise. It is hosted internally. I'd rate the solution seven out of ten based on the challenges we had surrounding migration. If a potential new user is new to the cloud and if they want to do an internal private cloud setup that is easy to deploy and push, I would recommend the new PCF.
My advice to others is to make sure Pivotal Cloud Foundry is the right solution for them. It could be the case where Microsoft Azure or Amazon AWS would be better. Pivotal Cloud Foundry
My advice to others is they should evaluate Pivotal Cloud Foundry to see if it fits their needs. It's comparable to some of the better-known names. From an acceptance point of view, I think it has lower adoption, but people should explore this further. I rate Pivotal Cloud Foundry seven out of ten.
What I saw recently was two big companies, trying to move from the PC to the cloud. They bought Pivotal Cloud Foundry and they are using it on a hybrid cloud. For example, they have two data centers and there are two installations of the Pivotal Cloud Foundry in each data center and they deploy microservices to each data center. They use external Amazon AWS to load balance. However, for some reason, the tendency right now for companies is to move to the Red Hat OpenShift, which is a commercial version of Kubernetes. I rate Pivotal Cloud Foundry a nine out of ten.
I would recommend the product to other users, and I would rate it 8 out of 10.
I would recommend this solution to others who are interested in using it. I would rate Pivotal Cloud Foundry an eight out of ten.
When we are working with our clients, we start with gathering the requirements and then create a proof of concept. Because we are meeting the requirements, our clients do not complain about this solution. My advice for anybody who is implementing this solution is to first go through the documentation or do a hands-on lab to learn about the product. I would rate this solution a seven out of ten.
I would rate the solution nine out of ten.