cloud native, why and what

Cloud Native, the why & what

@coteMarch 2016

1 Slides: http://cote.io/cloud-native-austin/

• @cote – Director, Technical Marketing at Pivotal for Pivotal Cloud Foundry

• Former industry analyst at 451 Research and RedMonk

• Corporate strategy & M&A at Dell

• Former software developer• Podcasts:

http://cote.io/podcasts• More: http://cote.io or

cote@pivotal.io

Hello!

2

Conclusions

3

• Organizations can no longer rely on long lasting competitive advantage to stay alive and profit. In an era of “transient advantage,” they must continually seek new business models and evolve existing ones.

• IT does not generally operate in the agile, small batch, “cloud native” ways that are required to be software defined businesses.

• The broad technologies are continuous delivery (the why), microservices (the what), and DevOps (the how).

• A “cloud platform” provides all of the development and operational capabilities needed to be cloud native.

• You can build and maintain your own platform (plus the original application you wanted!) or use a ready-made cloud platform

“If advantages eventually disappear, it only makes sense to have a process for filling your pipeline with new ones. This in turn means that, rather than being an on-again, off-again mishmash of projects, your innovation process needs to be carefully orchestrated.”- Prof. Rita McGrath, “Transient Advantage,” HBR, June 2013

“Cloud Native” is IT’s answer to transient advantage

4

Since 2000, 52% of the F500 are no longer

on the list

Sources: “Transient Advantage,” above; 2014 Constellation Research Summary, R. “Ray” Wang, Feb. 2014.

IT is usually doing it wrong

What is your IT

organization's role in business

innovation?

Source: ”Cutter Benchmark Review, May 2015, n=80 organizations.5

Cloud Native Business Theory

(1.) In an era of transient advantage, the inherit agility of software is one of the best strategic tools.

(2.) However, software in large organizations does not currently “work like that.”

(3.) The fix is changing how we think of the process of software, supported by cloud native technologies & practices.

Source: “Transient Advantage,” Rita McGrath, HBR, June 2013. 6

The Process

7

Discovering & delivering the software your customer actually wants

• Most organizations emphasize building to plan

• In reality, the “plan” constantly evolves

• Learning organizations explore & experiment

How most businesses think they’re doing

How smart businesses know they’re doing

8

Move from long-cycles to small batches

DESIGNDEVELOP

TEST

OPS

DEV

Customer

FeedbackProduct Release #1

Product Release #2

Customer

Delivery

- Reduced risk of delivering the wrong thing- Frequent feedback increases design quality, innovation- Increased visibility & controls for finance & GRC

9 Source: "Dear Developers, Small Batch Releases Are Your Friend," Coté, Feb 2016, also Feb 2016 DevOps column in The Register.

Benchmark your agile behaviors, plan catching-up as needed

Source: “Town Hall: Agile in the Enterprise,” Mike West, Nathan Wilson, Thomas Murphy, Dec 2015, Gartner AADI US conference.10

Go big with small batches

• Vitality drove engagement from 3% to 30%+

• Cue Apple Watch app: “Two people built the app and got it into the AppStore in five weeks.”

Source: Humana keynote, CF Summit 2015. "Application Modernization, Service By Microservice," Forrester, Dec 2015. See also BMC Software case study in The Concise Executive Guide to Agile and Cutter Executive Report, Vol. 9, No. 9, 2008.

"We did an analysis of hundreds of projects over a multi-year period. The ones that delivered in less than a quarter succeeded about 80% of the time, while the ones that lasted more than a year failed at about the same rate. We're simply not very good at large efforts.”

-Dev leader, large financial institution

11

The Tools

12

Continuous DeliveryRelease once every 6 months

More Bugs in production

Release early and oftenHigher Quality of Code

DevOpsNot my problem

Separate tools, varied incentives, opaque process

Shared responsibilityCommon incentives, tools, process and

culture

MicroservicesTightly coupled components

Slow deployment cycles waiting on integrated tests teams

Loosely coupled componentsAutomated deploy without waiting on

individual components

Platform, Standard Practices & Tools, Cloud Native Culture

Trad

ition

al IT

Clo

ud N

ativ

e

You’ll need a platform

Sources: "The cloud-native future," Casey West, O'Reilly Radar, Aug 2015; "Technical Dive into Cloud Native Application Platforms," Brian Gracely, Wikibon, Sep 2015.14

A cloud native platform is composed of three layers, that span & support the entire life-cycle of an application from development to production

12 factor apps & Microservices

Container Orchestration

Infrastructure Automation

Polyglot buildpacks & Spring Cloud

Elastic Runtime/Diego

BOSH

Cloud NativeApplication Frameworks

Cloud NativeRuntime Platform

Cloud NativeOperations

Cloud Native Empowered Culture

Source: slides in this section based on “Patterns of Cloud Native Architecture,” Agile 2015. 15

For more: transforming to cloud native

(1) GreenfieldProjects

(2) Dealing with

Legacy

(3)Corporate

Transformation

Get the free booklet at http://cote.io/pivotal16

Thanks!@cote | cote@pivotal.ioSlides: http://cote.io/cloud-native-austin/

“We are uncovering better ways of developing software by doing it and

helping others do it.”- The Agile Manifesto, 2001

17