Cloud Foundry for Developers: A quick dive into cloud-agnostic essentials for production-obsessed devs

Choices are generally a good thing, and when it comes to platforms for deploying applications, developers have plenty of them! Many options are "some assembly required", several take a unique (sometimes referred to as *proprietary*) approach to their solutions, and some...are open source, standards-compliant, infrastructure- and location-independent offerings that enable developers to focus more on their code and less on operational concerns. Isn't that why we want a platform in the first place? To enable us to deliver better code faster to production and to keep it running smoothly at scale?

The Cloud Foundry Foundation has over 70 members and shares a common core codebase. Cloud Foundry provides the platform (containerization, scaling, orchestration, networking, etc.) to enable true "cloud-native" applications...apps that don't care where they run in order to form responsive, resilient systems.

Join the presenter as he discusses and then demonstrates developer-focused features with *live coding and real deployments*. Come to this session to level up on Cloud Foundry!

Transcript

1. Cloud Foundry for Developers A quick dive into cloud-agnostic essentials for production-obsessed devs Mark Heckler Principal Technologist/Spring Developer Advocate Pivotal Software, Inc. www.thehecklers.com mark@thehecklers.com mheckler@pivotal.io @MkHeck
2. @mkheck @cloudfoundry @pivotalcf Who am I? • Author • Speaker • Software Architect/Developer • Java Champion • Time traveller
3. @mkheck @cloudfoundry @pivotalcf Why a PaaS?
4. @mkheck @cloudfoundry @pivotalcf –Onsi Fakhouri “Here is my source code Run it in the cloud for me I do not care how” “cf push” (a haiku)
5. @mkheck @cloudfoundry @pivotalcf Cloud Foundry overview • Foundation holds all IP • Over 65 (& counting!) members • Common codebase • Support for containers • You choose/control underlying IaaS • Public and on-premises options, one consistent API
6. @mkheck @cloudfoundry @pivotalcf Various commercial offerings
7. @mkheck @cloudfoundry @pivotalcf On Premises Public Cloud Infra
8. @mkheck @cloudfoundry @pivotalcf Images vs. Buildpacks Buildpacks • More flexible & mature capabilities within all CF variants • Container OS can be patched by admin w/o rebuilding app • App libs can be "freshened" with a simple app restage • Allow definition of env vars in manifest and afterward Docker images • Can use Docker images from public repository • Can control when container OS is patched (flip side: devs have responsibility for it) • Allow definition of env vars in Dockerfile (image) and afterward (pros/cons)
9. @mkheck @cloudfoundry @pivotalcf A few useful commands • cf l/login • cf h/help • cf a/apps • cf app • cf p/push • cf e/env • cf d/delete • cf logs • cf se/set-env • cf scale • cf m/marketplace • cf s/services • cf cs/create-services • cf bs/bind-services cf help shows ALL commands, cf <command> --help gives specifics
10. @mkheck @cloudfoundry @pivotalcf Show time!
11. @mkheck @cloudfoundry @pivotalcf Helpful resources • https://github.com/mkheck/cf4devs • https://docs.cloudfoundry.org/ • http://docs.pivotal.io/ • https://docs.docker.com/
12. @mkheck @cloudfoundry @pivotalcf Thanks for coming! @mkheck mark@thehecklers.com mheckler@pivotal.io