Overall Satisfaction with IBM Cloud Foundry
It ran our entire backend functionality. It is used across the entire organization and its impact is seen on every one of our customers. We used it to try to simplify our deployments, as they took a lot of time out of our day.
- Large collection of tools to integrate with.
- Growing application support.
- Bluemix has the ability to scale easily from very small to very large.
- Applications that were integrated had a feeling like they came from very different companies and organizations.
- Logins had to be performed often between different services, once a week the applications would change and we had to learn a different way to do the logins.
- Branding is important, but the names, like "Jazz" would get in the way of what the application did for us. So new developers would have to learn 5-6 new special websites just to do a single deployment. And one or two new changes a month to keep up with it.
- Deployments are easier than in a server up environment, though it takes some training.
- The service proved unreliable; if it didn't deploy, we just did it again until it worked.
- Amazon Elastic Compute Cloud (EC2) and Heroku
While IBM works well is when being used by large organizations, these other vendors work well with smaller organizations. We ended up being willing to pay more for Heroku, as they have such an easy-to-use service, and our deployments worked as expected every time.
It is suited to large businesses with somebody specifically in charge of deployments. He would be a person specifically paid to take care of all the machines through the Bluemix service. It is not a good situation when the teams are small, such as a three-person development team, because there is considerable maintenance that must be taught between them, and this costs a bit of time and hence money in that situation.