It wasn’t too long ago that artisans, bathed in the glow of molten metal, forged parts that would go on to make up bigger, more powerful machines. Today, we call those artisans developers. Instead of metal, they use bits and bytes in the cloud to forge a modern application architecture that supports public, private and hybrid application deployment. One that enables users and developers to move their applications wherever they need to go. And it’s built on a growing, vibrant ecosystem. Nowhere is this epic shift in how things are made more visible than the meteoric adoption of Cloud Foundry. In this talk, Chip Childers, VP of Technology for Cloud Foundry Foundation, will give attendees an inside look at the industry movements and the technological requirements that are driving Cloud Foundry's rapid adoption. Most importantly, he will walk through how organizations are responding to the challenge of continuous innovation, what's driving modern application architectures, and how the Cloud Foundry platform uses specific constraints in order to fulfill it's promise to application owners.

1. @chipchilders
Chip Childers, VP Technology
Cloud Foundry Foundation
The Platform for Forging Cloud Native
Applications

2. Since 2000, 52% of the Fortune
500 are no longer on the list

4. Continuous Innovation

5. Right-sizing digital innovation
Focused on cycle time optimization
Smaller teams and faster tools

6. Continuous
Integration
Continuous
Deployment
Continuous
Innovation

7. Continuous
Integration
Continuous
Deployment
Continuous
Innovation

8. waterscrumfall

9. Continuous
Integration
Continuous
Deployment
Continuous
Innovation

11. “Any organization that designs
a system (defined broadly) will
produce a design whose
structure is a copy of the
organization's communication
structure.
Melvyn Conway, 1967

12. Two-pizza teams
Silo-breaking

13. Ephemeral
Scalable
Agile

15. Microservices
Containers
12-Factor Applications

16. Microservices are great, but they require:
rapid provisioning
basic monitoring
rapid application deployment
devops culture
Per Martin Fowler

18. • Use declarative formats for setup automation, to minimize time and
cost for new developers joining the project;
• Have a clean contract with the underlying OS, offering maximum
portability between execution environments;
• Are suitable for deployment on modern cloud platforms, obviating
the need for servers and systems administration;
• Minimize divergence between development and production,
enabling continuous deployment for maximum agility;
• And can scale up without significant changes to tooling,
architecture, or development practices.

19. But even that’s not enough…

20. • Role based access to resources: the right
people should be able to do things and the
wrong people shouldn’t
• Run specified bits on demand: take code, put
it together with all the rest of the things it
needs and and get it running
• Coordinate cross service configurations: in a
service oriented world, services need to be
configured to connect with each other
• Route public requests to running bits: the
next big thing needs access to the internet
• Read and write persistent data: data has to
live somewhere
• Add and remove resources: scaling is a great
problem to have, but still
• Isolate resources and failures without
isolation and decoupling, that is one big
distributed single point of failure
• Measure performance/health: can’t manage
what you don’t measure
• Detect and determine failure: sometimes,
things get real… but how do you know
• Recover failures: someone is going to have
to clean this mess
• Work tomorrow: when everything you’ve
thought to be true has been shown not to

21. Containers Are Awesome, but Not Enough

22. We’re going to need a platform

23. Is BASH a platform?
Is config mgmt with $YOURFAVTOOL?

24. Borg
Mesos
Cloud
Foundry
Omega
Kubernetes
cgroups
Docker
OCI
rkt/appc
LXC

25. Carrier Networking
Datacenter Networking
Datacenter Operating Systems
Hardware
Virtualization
Operating Systems
Application Platforms
Programming Frameworks
Containers
Open Container
Initiative

26. Unit of Value
IaaS == Virtual Machine
• Opaque to the system
• Orchestration is post-hoc
• System changes are imperative
(“launch” stuff)
App Platform == Application
• Containers are transparent
• Lifecycle is fully managed
• System changes are
declarative (manifest.yml)

27. Platforms make promises
Constraints are the contract that
allows a platform to keep
promises

28. Here is my source code
Run it on the cloud for me
I do not care how
Cloud Foundry Haiku
Onsi Fakhouri

29. .war .jar
dependencies
libraries
service manifest
App App App
LB
DB
Multi-server run time
environment(s)
.tar.gz
Turning this: Into this:

30. • Auto-detect frameworks
• Link to App Platform
• Self-service deploy
• Dynamic routing
• A/B versioning
• Live upgrades
• Self-service
removal
• Elastic scale
• Integrated HA
• Log aggregation
• Policy and Auth

31. target <mycf>
push <myapp>
create-service <myservice>
bind <myapp> <myservice>
start <myapp>
scale <myapp> -i 100
…
cf
App
DB
LB
App App

32. Where’s the container in this
story?

33. Prescriptive
CHRONOS
scheduler.next
container.next
Assembly

34. Prescriptive
CHRONOS
scheduler.next
container.next
Assembly
runC

35. Prescriptive
CHRONOS
scheduler.next
gorouter
CloudController Auth
Loggregator
Staging
Buildpacks
BOSH
Service Broker
Diego
Garden
etcd
Core
Services
container.next
Assembly
runC

36. Prescriptive Assembly
CHRONOS
scheduler.next
gorouter
CloudController Auth
Loggregator
Staging
Buildpacks
BOSH
Service Broker
Diego
etcd
Core
Services
container.nextrunC

37. = + +
Contents Processes
?
?
Isolation Rules
PID
User
Network
cgroups cflinuxfs2

38. Anatomy of a cf push (abridged)

39. Let’s talk about Buildpacks / Staging
• Ruby code that detects language,
frameworks, whatnot…
• Compiles the code into executable
binaries (*)
/bin/detect < Am I supposed to run?
/bin/compile < Build the thing
/bin/release < Pass along potential metadata
cflinuxfs2

40. That was all about 12 factor
apps…
What about services?

42. .war .jar
dependencies
libraries
service manifest
App App App
LB
DB
Multi-server run time
environment(s)
.tar.gz
Turning this: Into this:

43. Demo time!

44. The Cloud Native Advantage:
Simple Patterns
Highly Automated
Scaled with Ease

46. A platform is a promise that the products
will function in ways beyond what’s “written
on the box”; that the product is extensible
and has value provided by an
ecosystem bigger than the original
vendor.
Horace Dediu, 2011
http://www.asymco.com/2011/02/25/the-platform-as-a-promise/

50. We’re rebalancing the system towards user-driven
roadmaps and control of the upstream project.
We’re building support for specific industry
clusters in Financial Services, Industrial IoT, and
Telecommunications.

51. We’re focusing on certification to guarantee
portability of apps across clouds.
Make it lasting and durable.
Build the ecosystem of opportunity.

52. cfsummit.com

53. @chipchilders
Learn more at cloudfoundry.org
Thanks.