Ensuring Cloud Native Success: The Greenfield Journey
21
1 1 Ensuring Cloud Native Success: The Greenfield Journey
-
Upload
pivotal -
Category
Technology
-
view
1.374 -
download
0
Transcript of Ensuring Cloud Native Success: The Greenfield Journey
11
Ensuring Cloud Native Success: The Greenfield Journey
2
Use greenfield projects to learn the new way Why do this? To becoming a software defined business Change your behaviors to change your process Turning “failing” into “learning” Be successful at a small series of projects Staff your team with every role needed to be successful Strict testing to hold back calcifying technical debt Use 12 factor app principles to create cloud ready applications Architect with microservices in mind Avoid building your own platform unless that’s your actual product Expand with internal marketing, summits, etc.
3
@cote – Director, Technical Marketing at Pivotal for Pivotal Cloud Foundry
Former industry analyst at 451 Research and RedMonk
Corporate Strategy & M&A at Dell Software developer Podcasts: cote.io/podcasts FierceDevOps columnist More: http://cote.io or
Hello!
44
Why?
5
Source: "Gartner Says Modernization and Digital Transformation Projects Are Behind Growth in Enterprise Application Software Market", August 2015. For more “business drivers” see “The Three Horsemen of the Digital Apocalypse Considered.”
will be "build," not "buy.
Gartner predicts that by 2020,
75 percent of applications supporting digital business
Custom written software is becoming a key competitive advantage
6
The goal is to achieve continuous delivery
Build Test/Verify Package repository
VersionControl
InfrastructurePlatform
(IaaS, PaaS, VMs)
ProductionConcerns
(monitoring, scaling, etc.)
Feedback Loop
Specify Code
77
Most advice looks like this…
8
The Three “Journeys”
Greenfield
• Brand new• Little integration with
existing IT• Rarely “mission critical”
Legacy
• Makes all the money• Fragile, change is high
risk• Can consume all
corporate attention
Transformation
• Targets entire organization
• Benefits of scale• “Culture” change drives
successDec 1st, 10am PT/ 12pm
CT/ 1pm ETDec 15th, 10am PT/ 12pm CT/ 1pm ET
Nov 5th , 10am PT/ 12pm CT/ 1pm ET
99
Greenfield
10
Change your behaviors to change your processes
F100 CTO: “But Netflix has a superstar dev team, we don’t!”
@adrianco:“We hired them from you.”
Source: @blueboxjesse, Oct 2014. See also “There is no talent shortage.”
11
Turn “failure” into “learning”
How most businesses think they’re
doingHow smart businesses
know they’re doing
First step: admit you have no idea what’s going on
12
Be successful* at a small series of projects* Don’t talk a lot about the failures
• Vitality drove engagement from 3% to 30%+
• Second project, MyHealth
• Cue Apple Watch app in 5 weeks
Source: Humana keynote, CF Summit 2015. See also BMC Software case study in The Concise Executive Guide to Agile and Cutter Executive Report, Vol. 9, No. 9, 2008.
13
Staff your team with every role needed to deliver
Two pizza’s worth of:• Dev• Ops• Design• Product• QA• ?
Source: Pivotal SafeMeds scrapbook.
14
Strict testing to hold back calcifying technical debt
QA - automated testing to avoid technical debt, move fast
Uptime - testing for resiliency in production
Design quality - do people actually find your software useful?
Improvement - testing your process
15
Use 12 factor app principles to create cloud ready applications A set of best practices
for developing and deploying cloud-native software.
Practices translate into platform features and workflow requirements.
Codebase Dependencies Config Backing Services
Build, Release,
RunProcesses Port
BindingConcurrenc
y
DisposabilityDev/Prod
Parity Logs Admin Processes
Source: “The Twelve-Factor App.”
16
Architect with microservices in mind Decompose everything into
services Think of *nix style pipes on the
CLI, but in a distrusted system Each service is owned by a team
and indepdent A black-box with a well done API Benefits: scale, comprehensibility,
org. agility
Free book: bit.ly/cloud-native-book
17
Container Scheduling
Application Framework
ServicesPlatform Runtime
Routing DatabaseConfigurationService Discovery
Big Data
Object Storage
Mobile
Build CI
User ProvidedLogging & Metrics Messaging
Circuit Breakers12 Factor Apps RESTful
ServicesMicroservices
.NETSpring Boot Node.jsRuby on Rails
Operations Zero Downtime Deployments
Failover & Recovery Scaling Security
PatchingPlatformUpgrades
Infrastructure
OpenStack AmazonVMware
18
Expand with internal marketing, summits, etc.
• Repeated boasting
• Training at internal summits
Source: “Humana Leads Charge for Digital Transformation in Louisville.”
• Evangelism
• “Labs” - CoE’s that don’t suck
19
What’s Next?
Greenfield
Read the original piece, with more details and advice:
cote.io/cloud-native-journey/
Legacy
• Makes all the money• Fragile, change is high
risk• Can consume all
corporate attention
Transformation
• Targets entire organization
• Benefits of scale• “Culture” change drives
success
Dec 1st, 10am PT/ 12pm CT/ 1pm ET
Dec 15th , 10am PT/ 12pm CT/ 1pm ET
BUILT FOR THE SPEED OF BUSINESS
