CloudFoundry vs IBM Cloud Foundry

• Ease of use, up and running in no time.
• Well documented
• Supports most common languages such as Java, Node.js, etc.
• Open source with a big community contributing to it.

Read full review

• Keeps things more standardized, ring fenced and thus easier for the end user to use
• Open source, allowing for a wide group for education, auto and support
• Developing at pace to keep up with the ever changing needs of the industry from on / off premise, public and private

Read full review

• 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.

Read full review

• Sometimes the API Connect GUIs don't cleanly disengage after attaching models or updating schema and it is hard to know what has been written successfully and which (if any) models or tables were missed. I shouldn't have to manually check through a list of 377 models to find the ones in and out of a list on either models, folder or database tables. Printing a summary even in logs which did a "diff" sort of thing between 'task-set' and 'task-completed' (referring to attaching models or updating schema as tasks here as 'tasks').
• Provide access to Postgres Database in Sydney datacentre for Australia.
• Clearer documentation around setting up a secure (referring to SSL and certificate setup here) server on eg, chubby1.au-sydney.mybluemix.net.
• Allow a ramp in pricing onto the Blockchains. We will not be able to afford it until quite a few years into production, even if we launch successfully.

Read full review

• 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.

Read full review

• Bluemix has allowed me to effectively serve the App industry more recently, especially with the new visual design implemented recently.
• BlueMix offers a lot more customization of the Platform, rather than Infrastructure, giving me a big edge over other companies offering only AWS or Azure cloud services, and brings a lot more apparent value to my business.
• The additional features, especially the Watson service subset offers a HUGE range of new and innovative technologies, especially in the realm of AI, that encourages my clients to test out new potential features, which leads to more sales as they increase there platform size and capability.

Read full review