[parasubvert]

Interesting to see Cloud Foundry take off this year after many years of being more of a curiosity on its own island.

I personally didn't get it until I saw Docker a couple of years ago and wondered "how will we operate all of these apps, services or even the servers they run on without playing yet another shell game and resorting back to traditional shit IT?". And that brought me back to Cloud Foundry and BOSH, to the point where I quit my old job and joined Pivotal.

[zaksoup]

This is a huge validation of everything we've been saying and working on at Pivotal. In order to be successful at running software at scale you need your operations to get out of your way as a developer, and you need tools and architecture that make being an operator painless.

That's the goal with CF and Bosh, and it's clear that it pays off.

[frabcus]

How are you finding Cloud Foundry? Is it good?

I've looked quickly at it, but unlike (say) Heroku, found it hard to know where to start to host a simple app.

[parasubvert]

Pivotal Web Services - Run.pivotal.io - is the CF equivalent to Heroku. Documentation is at docs.run.pivotal.io. IBM has one at Bluemix.net as well.

CF is very good if you want to run a cloud native / 12 factor app. It's also rapidly evolving to run rich workloads (TCP router is coming, .NET is in beta).

I would say CF is more flexible at the kinds of apps and services it can run as the buildpacks tend to be more sophisticated forks of the Heroku buildpacks, or new from scratch buildpacks (like PHP, Or Java). Docker images should be hostable in the near future as well.

Whereas the service levels and instance sizing flexibility available from Heroku tends to be richer.

This is a function of where both companies make their money. Heroku only makes money from their public cloud, whereas Pivotal is focused on selling high end subscriptions for those who want to run their own private CF on Amazon or VMware or OpenStack.

[wslack]

We have doc stuff here: https://docs.cloud.gov/