Upload
chip-childers
View
917
Download
0
Embed Size (px)
Citation preview
@chipchildersChip Childers, VP Technology
Cloud Foundry Foundation
Going Cloud Native - It takes a Platform
@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, Redmonkhttp://redmonk.com/sogrady/2015/07/24/cloud-native-implications/
@chipchilders
Focus on Takt TimeDefinition: the desired time between units of production output,
synchronized to customer demand
http://www.strategosinc.com/takt_time.htm
@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.
@chipchilders
RBAC
SecurityHealth
Management
Performance Management
Failure Detection
Resiliency
Container Management
Resource Schedulin
gData
Persistence
Routing Build Process
Service Discovery
Service Brokerage
Log Aggregation
Identity Managemen
t
Failure Recover
y
@chipchilders
Platforms make promises
Constraints are the contract that allows a platform to
keep promises
@chipchilders
Here is my source codeRun it on the cloud for meI do not care how
Cloud Foundry HaikuOnsi Fakhouri