Ensuring Cloud Native Success: The Greenfield Journey

19
1 1 Ensuring Cloud Native Success: The Greenfield Journey Nov. 2015 Slides: http:// cote.io /greenfield-journey/

Transcript of Ensuring Cloud Native Success: The Greenfield Journey

Page 1: Ensuring Cloud Native Success: The Greenfield Journey

11

Ensuring Cloud Native Success: The Greenfield Journey Nov. 2015

Slides: http://cote.io/greenfield-journey/

Page 2: Ensuring Cloud Native Success: The Greenfield Journey

2

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

Nov 5th

, 12 central Dec 1st

, 12 central Dec 15th, 12 central

Page 3: Ensuring Cloud Native Success: The Greenfield Journey

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

[email protected]

Hello!

Page 4: Ensuring Cloud Native Success: The Greenfield Journey

44

Why?

Page 5: Ensuring Cloud Native Success: The Greenfield Journey

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

Page 6: Ensuring Cloud Native Success: The Greenfield Journey

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

Page 7: Ensuring Cloud Native Success: The Greenfield Journey

77

Most advice looks like this…

Page 8: Ensuring Cloud Native Success: The Greenfield Journey

88

Greenfield

Page 9: Ensuring Cloud Native Success: The Greenfield Journey

9

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.”

Page 10: Ensuring Cloud Native Success: The Greenfield Journey

10

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

Page 11: Ensuring Cloud Native Success: The Greenfield Journey

11

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.

Page 12: Ensuring Cloud Native Success: The Greenfield Journey

12

Staff your team with every role needed to deliver

Two pizza’s worth of:• Dev• Ops• Design• Product• QA• ?

Source: Pivotal SafeMeds scrapbook.

Page 13: Ensuring Cloud Native Success: The Greenfield Journey

13

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

Page 14: Ensuring Cloud Native Success: The Greenfield Journey

14

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.”

Page 15: Ensuring Cloud Native Success: The Greenfield Journey

15

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

Page 16: Ensuring Cloud Native Success: The Greenfield Journey

16

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

Page 17: Ensuring Cloud Native Success: The Greenfield Journey

17

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

Page 19: Ensuring Cloud Native Success: The Greenfield Journey

1919

Thanks!@cote | [email protected]

Slides: http://cote.io/greenfield-journey/