Chip Childers discusses the significance of cloud-native technologies, emphasizing traits such as containerization, micro-services, automation, and high uptime. He outlines essential principles for effective cloud applications, including portability, continuous deployment, and minimal divergence between development and production. The role of platforms is highlighted, with a focus on how they create constraints that enable creativity and efficiency in deploying applications.

1. @chipchilders
Chip Childers, VP Technology
Cloud Foundry Foundation
Going Cloud Native - It takes a Platform

2. @chipchilders
Why does Cloud Native matter?

3. @chipchilders
The Cloud Native Advantage:
Simple Patterns
Highly Automated
Scaled with Ease

4. @chipchilders
There is a rough consensus on many Cloud Native traits.
Containers as an atomic unit, for example. Micro-services
as the means of both construction and communication.
Platform independence. Multiple language support.
Automation as a feature of everything from build to
deployment. High uptime. Ephemeral infrastructure
(cattle not pets). And so on.
Stephen O’Grady, Redmonk
http://redmonk.com/sogrady/2015/07/24/cloud-native-implications/

5. @chipchilders
It’s not just about technology

6. @chipchilders
Industrializing the Craft

7. @chipchilders
Focus on Takt Time
Definition: the desired time between units of production output, synchronized
to customer demand
http://www.strategosinc.com/takt_time.htm

8. @chipchilders
Emergent engineering principles

9. @chipchilders
12 Factors
• 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.

10. @chipchilders
But even that’s not enough…

11. @chipchilders
RBAC
Security
Health
Management
Performance
Management
Failure
Detection
ResiliencyContainer Management
Resource
Scheduling
Data
Persistence
Routing
Build
Process
Service
Discovery
Service
Brokerage
Log
Aggregation
Identity
Management
Failure
Recovery

12. @chipchilders
You’re going to need a platform

13. @chipchilders
Platforms make promises
Constraints are the contract that
allows a platform to keep
promises

14. @chipchilders
The right constraints free us to be
creative where it matters

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

16. @chipchilders
Chip Childers, VP Technology
Cloud Foundry Foundation
Thanks!