IBM Cloud Foundry vs Kubernetes

• 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

• Cost-effectiveness, Kubernetes is free and open source.
• Scalability, Kubernetes works regardless of how many pods it's managing; be it ten or a thousand.
• Low overhead, Kubernetes adds very little performance cost per developer per machine. The benefits of having a managed system vastly outweigh the minor performance cost.
• Large market share, Kubernetes is one of the top container orchestration tools used by developers today. This has been immensely helpful when finding new talent who are familiar with Kubernetes.

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

• Speed of error detection - many times, in attempting to fix a problem, I found that kubernetes just had a delay in handling an automated fix. By changing the system, I was playing a cat and mouse game with kubernetes' attempts to auto-fix the error.
• Sensible logging - many of the logs are difficult to decipher and too verbose to be useful.
• The learning curve is high - it took many months of working with Google, in which both I and Google Support Engineers learned a lot about how Kubernetes works. The learning curve is not for people looking for quick and easy out of the box.

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

• We switched from Chef, so we got a HUGE amount of ROI by switching our microservices over to Kubernetes 8. A lot less code, a lot easier to test, and immutable images means we have just one build and that artifact goes through all the environments.
• Automated deploys are SUPER easy with Kubernetes 8. We just have simple scripts listening on a GitHub repo for changes that applies/creates all the Kubernetes 8 pieces we need. Everyone has the power to deploy to any of the clusters through code and code reviews.
• Shrunk our devops need dramatically, everything just works.

Read full review