Head of Engineering at a financial services firm with 10,001+ employees
Real User
Aug 23, 2023
Something that can be done better is canary deployment. So, right now, we're using blue-green deployment. The support for canary deployment would be nice. A few things, such as what OpenShift does better are cluster management. Like, you can manage the entire thing together. Currently, it's possible to manage all the clusters, especially when it comes to cluster management using straightforward configuration. As of now, we have to handle each application instance individually, which means servicing them one by one. It would be better if we could perform these actions as a group or in a more streamlined manner. One more downside is actually the cost of this environment. So, major downside of Pivotal, it's the cost. So, the runtime running costs are very high. Extremely high.
Assistant to Vice President at a consultancy with 10,001+ employees
Real User
Top 20
Mar 9, 2023
There is a lot of uncertainty surrounding the future of Pivotal Cloud Foundry. Constantly being adopted by new organizations makes it a risky investment for companies, as there is no guarantee that the solution will still exist in a few years. The technical support has room for improvement.
Now the organization is thinking about moving everything to a public cloud. The private cloud microservice components are not able to move directly to public clouds, including Amazon or Google. It is not fully containerized. Therefore, you have to make more changes in order to move it to a public cloud. That is something that is not straightforward. We'd like it if they made it easier to move to a public cloud in future releases. I'd like to see a larger service offering. For example, Amazon offers authentication, contained management, and storage-based services. I still need to explore this solution more, however, if they do not offer as many services, they should work to broaden their offering. If you want to use Kafka or anything that's a Q-based mechanism, which should be out of the box, from the PCF itself, it should be so that we don't have to communicate with a different server altogether. I'm not sure if that is feasible with PCF itself. We've had some challenges with graphic libraries.
Lead System Operation Engineer at a tech services company with 51-200 employees
MSP
Nov 14, 2022
An easier way to switch between data centres can be included in the next release. We have no active-active scenario, but at some endpoints, we have to shut down first and then only run the application on BCP. In that situation, we see a switch available, but it is a little tricky for new members. Additionally, there are no synthetic application monitoring and real-time monitoring features and they should be included.
Pivotal Cloud Foundry could improve the documentation. They are good, but they could improve more. Additionally, it would be beneficial if there were more use case examples. In a future release, it could be helpful to have a graphical interface rather than only the command line interface.
Tech Lead at a retailer with 5,001-10,000 employees
Real User
Oct 21, 2020
Having support for other integrated tools, such as Kubernetes, would be useful. The interface is okay, but it's not that advanced. It could be improved. The initial setup could be simplified. In the next release, I would like to see easy integration with external tools. For example, it should be easy to integrate with Kubernetes. It would also be helpful to have a notification for when you are using other applications that require specific hardware. For example, when you are running your application, to have it say that it should be running on this port for the node on the cloud.
Sr. Cloud Architect at Intuitive Technology Partners
Real User
Apr 28, 2020
The user interface should be simpler to navigate because it t can take time for users to learn it. They can refer to the documentation and YouTube videos, but the navigation is still a concern. It would be great if the setup and deployment were easier to do. I would like to see the vendor create hands-on labs that help to give the user experience with the look and feel of the software. This would help them to better navigate the interface when it comes to configuration, management, integrating it with different cloud platforms, and using it.
Software Engineer at a comms service provider with 1-10 employees
Real User
Sep 19, 2019
In the next release, they should offer additional applications for the databases, and improve the deployment experience. They should offer more information to consultants in the form of tips and other details to help them better understand the product.
Pivotal Cloud Foundry is a scalable cloud platform known for its deployment ease, monitoring, and auto-healing capabilities. It supports Java and Spring Cloud frameworks, offering a stable environment for microservices and seamless CI/CD integration.Pivotal Cloud Foundry facilitates cloud-based application development, focusing on private cloud security and developer-friendly tools. Open-source advantages lead to enhanced performance and innovation, providing robust deployment crucial for...
Something that can be done better is canary deployment. So, right now, we're using blue-green deployment. The support for canary deployment would be nice. A few things, such as what OpenShift does better are cluster management. Like, you can manage the entire thing together. Currently, it's possible to manage all the clusters, especially when it comes to cluster management using straightforward configuration. As of now, we have to handle each application instance individually, which means servicing them one by one. It would be better if we could perform these actions as a group or in a more streamlined manner. One more downside is actually the cost of this environment. So, major downside of Pivotal, it's the cost. So, the runtime running costs are very high. Extremely high.
Pivotal Cloud Foundry doesn't have certain advanced features. So, the solution should consider adding more advanced features within the tool.
There is a lot of uncertainty surrounding the future of Pivotal Cloud Foundry. Constantly being adopted by new organizations makes it a risky investment for companies, as there is no guarantee that the solution will still exist in a few years. The technical support has room for improvement.
Now the organization is thinking about moving everything to a public cloud. The private cloud microservice components are not able to move directly to public clouds, including Amazon or Google. It is not fully containerized. Therefore, you have to make more changes in order to move it to a public cloud. That is something that is not straightforward. We'd like it if they made it easier to move to a public cloud in future releases. I'd like to see a larger service offering. For example, Amazon offers authentication, contained management, and storage-based services. I still need to explore this solution more, however, if they do not offer as many services, they should work to broaden their offering. If you want to use Kafka or anything that's a Q-based mechanism, which should be out of the box, from the PCF itself, it should be so that we don't have to communicate with a different server altogether. I'm not sure if that is feasible with PCF itself. We've had some challenges with graphic libraries.
An easier way to switch between data centres can be included in the next release. We have no active-active scenario, but at some endpoints, we have to shut down first and then only run the application on BCP. In that situation, we see a switch available, but it is a little tricky for new members. Additionally, there are no synthetic application monitoring and real-time monitoring features and they should be included.
Pivotal Cloud Foundry could improve the documentation. They are good, but they could improve more. Additionally, it would be beneficial if there were more use case examples. In a future release, it could be helpful to have a graphical interface rather than only the command line interface.
Pivotal Cloud Foundry could improve on the technology it is a bit complex.
It is not straightforward to setup.
Having support for other integrated tools, such as Kubernetes, would be useful. The interface is okay, but it's not that advanced. It could be improved. The initial setup could be simplified. In the next release, I would like to see easy integration with external tools. For example, it should be easy to integrate with Kubernetes. It would also be helpful to have a notification for when you are using other applications that require specific hardware. For example, when you are running your application, to have it say that it should be running on this port for the node on the cloud.
The user interface should be simpler to navigate because it t can take time for users to learn it. They can refer to the documentation and YouTube videos, but the navigation is still a concern. It would be great if the setup and deployment were easier to do. I would like to see the vendor create hands-on labs that help to give the user experience with the look and feel of the software. This would help them to better navigate the interface when it comes to configuration, management, integrating it with different cloud platforms, and using it.
In the next release, they should offer additional applications for the databases, and improve the deployment experience. They should offer more information to consultants in the form of tips and other details to help them better understand the product.