CloudFoundry vs. IBM Cloud Virtual Servers for VPC

It's well suited if:

• The organization has large number of applications that needs to be deployed frequently.
• The organization is tied to the DevOps mindset.
• The organization has programs in different languages.
• The applications does not need EJB's support that servers like web logic provide.

It's less suited if:

• The applications needs security configuration within the same CloudFoundry instance.
• The organization, for whatever reason does not want developers to manage the instances.

Incentivized

One scenario that immediately came to my mind was large-scale data processing, IBM Cloud Virtual Servers is well-suited for organizations that require high-performance computing capabilities, particularly when processing large amounts of data. It can also be useful for companies or organizations that wish to migrate their workplace to the cloud and it may suite companies that have strict compliance requirements since the servers have robust security features.

Incentivized

• Support for Orgs and Spaces that allow for managing users and deployables within a large organization.
• Easy deployment, deploying code is as simple as executing single line from CLI, thanks to build-packs.
• Solid and rich CLI, that allows for various operations on the instance.
• Isolated Virtual Machines called Droplets, that provide clean run time environment for the code. This used to be a problem with Weblogic and other application servers, where multiple applications are run on the same cluster and they share resources.
• SSH capability for the droplet (isolated VM's are called droplets), that allows for real time viewing of the App code while the application is running.
• Support for multiple languages, thanks to build-packs.
• Support for horizontal scaling, scaling an instance horizontally is a breeze.
• Support for configuring environment variable using the service bindings.
• Supports memory and disk space limit allocation for individual applications.
• Supports API's as well as workers (processes without endpoints)
• Supports blue-green deployment with minimal down time

Incentivized

• Scalability: IBM Cloud Virtual Servers enable businesses to simply and quickly scale up or down the resources they require in response to changing business demands. This enables firms to respond to traffic spikes, requests for new services, or changes in business size without the need for additional hardware purchases or maintenance.
• Cost savings: By employing virtual servers in the cloud, enterprises can decrease capital expenditures for hardware and infrastructure while also lowering ongoing operational expenses by removing server maintenance and management costs. This can result in significant cost savings for enterprises, particularly those that need to raise or decrease their computer capacity fast and easily.
• High availability: IBM Cloud Virtual Servers is built with high availability in mind, giving enterprises the certainty that their applications and data will be available and accessible even if hardware fails or other disruptions occur. This assists enterprises in maintaining business continuity and lowering the chance of downtime, which is crucial for firms that rely on 24/7 access to their systems. Furthermore, IBM's comprehensive network and security features aid in the prevention of data breaches and other security risks, assuring the availability and reliability of their applications and data.

Incentivized

• Does not support stateful containers and that would be a nice to have.
• Supports showing logs, but does not persist the logs anywhere. This makes relying on Cloud Foundry's logs very unreliable. The logs have to be persisted using other third party tools like Elk and Kibana.

Incentivized

• It would also be nice if there were more templates to choose from when creating a server. Right now there are only a few options, and we'd like to see more variety.
• We'd like to see the ability to create server groups. This would make it easier to manage a large number of servers since we could do all of the updates and management tasks for them at once.
• There doesn't seem to be a way to automatically install updates on all of the virtual servers. We have to go in and manually update each one, which can be time-consuming. It would be really nice if automatic updates can be done.

Incentivized

It has a flexible and affordable pricing, easy to configure and manage. It is easy to spawn one or multiple instances and have them up and running in no time

Incentivized

Always available when you need an instance.

Incentivized

Most of the instances work on hypervisors with good processors, but not all of them.

Incentivized

It is adequate, but you need to be ready to argue your point - which is fair enough, I suppose, but being given the opposite of the benefit of the doubt every time does not necessarily result in an enjoyable user experience.

Incentivized

We did not use IBM professional services to implement IBM Cloud Virtual Servers.

Incentivized

While Docker shines in providing support for volumes and stateful instances, Cloud foundry shines in providing support for deploying stateless services. Heroku shines in integrating with Git and using commits to git as hooks to trigger deployments right from the command line. But it does not provide on-premise solution that Cloud foundry provides.

Incentivized

IBM Cloud Virtual Servers offer more customization options than Amazon EC2, with the ability to select from a range of operating systems, storage types, and network configurations. IBM also provides a wide range of tools and services to help manage and optimize your virtual servers, including a web-based console, CLI, and API.

AWS EC2 is a more managed platform, with a focus on providing a simple and easy-to-use interface. Amazon provides a range of predefined instance types, each with different specs and pricing, to make it easy to find the right option for your needs. AWS also offers a number of management and monitoring tools, but these are often more basic than what is available from IBM.

Incentivized

It worked well for us in the beginning, it works well for us when we have more instances.

Incentivized

• Positive impact, since it simplifies the deployment time by a huge margin. Without cloud foundry, deploying a code needs coordination with infrastructure teams, while with cloud foundry, its a simple one line command. This reduces the deployment time from at least few hours to few minutes. Faster deployments promote faster dev cycle iterations.
• Code maintenance such as upgrading a Node or Java version is as simple as updating the build-pack. Without cloud foundry, using web logic, the specific version only supports a specific version of Java. So updating the version involves upgrading the version of web logic that needs to involve few teams. So without cloud foundry, it takes at least few days, with cloud foundry, its a matter of few mins.
• Overall, happier Developers and thats harder to quantify.

Incentivized

• Supports businesses who want compute power on demand (instances are ready within minutes).
• It can give you access to a 32-core CPU at $0.29 for short running or interruptible processes - enabling cost-efficient number crunching.
• Given me a taste of the powers of remote compute power for compilation and development.

Incentivized