Speaker: Coté, Director, Technical Marketing, Pivotal
Are you being asked to put more cloud in your strategy? If you’re like most people, the answer is a definite yes. The word “cloud” can mean so many things, however, that making an actionable strategy is impossible. At Pivotal, we divide cloud into two distinct parts: migrating as many legacy applications into SaaS as possible and focusing on perfecting the software you build in-house that runs your business. Gartner is predicting that by 2020, 75% of applications used to support digital businesses will be built in-house. If you’re one of these companies, you’ll need to quickly evaluate how you develop and run your custom written software.
We believe that soon, every company will either be a software company or losing to a competitor who is. It’s time to focus on the craft of managing the software development life-cycle, and this brief, but dense webinar will help launch your efforts to become a software defined business.
Join us for the first installment of this 3 part webinar session: The Greenfield Journey https://pivotal.io/platform/webinar/ensuring-cloud-native-success-the-greenfield-journey
2. 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. 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 cote@pivotal.io
Hello!
5. 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. 6
The goal is to achieve continuous delivery
Build Test/Verify
Package
repository
Version
Control
Infrastructure
Platform
(IaaS, PaaS, VMs)
Production
Concerns
(monitoring, scaling, etc.)
Feedback Loop
Specify Code
8. 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 success
Dec 1st, 10am PT/ 12pm
CT/ 1pm ET
Dec 15th, 10am PT/
12pm CT/ 1pm ET
Nov 5th , 10am PT/ 12pm
CT/ 1pm ET
10. 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. 11
Turn “failure” into “learning”
How most
businesses
think they’re
doing
How smart businesses
know they’re doing
First step: admit you have no idea what’s going on
12. 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. 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. 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. 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
Dependencie
s Config
Backing
Services
Build,
Release,
Run
Processes
Port
Binding
Concurrency
Disposability
Dev/Prod
Parity
Logs
Admin
Processes
Source: “The Twelve-Factor App.”
16. 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. 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
Services
Microservices
.NETSpring Boot Node.jsRuby on Rails
Operations
Zero Downtime
Deployments
Failover &
Recovery
Scaling
Security
Patching
Platform
Upgrades
Infrastructure OpenStack AmazonVMware
18. 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. 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
The Phoenix Project is a re-write of The Goal.
Focus your resources (time, money, effort) on the first two activities, that’s where you can compete.
Leave the rest to other folks, out source to tools and platforms.
Beware of “the fat boy scout” as outlined in The Goal. If you’re super fast in the left side but then slow on the right, it won’t matter. When marching, you’re only as fast as your slowest person.
Most of what you’ll be doing is changing your behabior, how you do things.
Cloud native is about doing things in new ways to get new results. That means you’ll be…doing things differently.
The way to do this is to change behavior. At the management level, it’s change management, something we’ll talk about more in the transformation discussion.
But, for now: try new things!