pivotal power lunch - why cloud native?

Power Lunch Series – Why Cloud Native? Sufyaan Kazi

3 © 2016 Pivotal Software, Inc. All rights reserved.

Cloud Native Power Lunch Series

https://youtu.be/f-H1aJJpm0U

Who are Pivotal?



Powering Digital Transformation Pivotal enables enterprises to provide

modern software-driven experiences for their customers and workforces.



Trusted partner for IT innovation and digital transformation New mode for cloud-computing – open and enterprise ready Gold standard for modern software development



Sufyaan Kazi [email protected] @sufyaan_kazi



Introduction



Topics in the Power Lunch Series Why Cloud Native? 18 August 2016

How to Architect & Develop Cloud Native Applications? (Part 1 & 2) 20 September & 6 October 2016

How to Modernise Legacy Applications 25 October 2016

How to enable Continuous Delivery of Software into Production 10 November

How to Operate Cloud Native Applications 6 & 20 December 2016



KEY TRENDS

The cost and ubiquity of computing enables cloud native software companies to reshape the world

Near-free computing costs

Mobile devices and connectivity

Ubiquity of embedded sensors

Global scale of operations


Cloud Native Power Lunch Series Source: JPMorgan Chase Annual Shareholder Letter (2015)

“Silicon Valley is coming…and they all want to eat our lunch.” - Jamie Dimon CEO, JPMorgan Chase



AUTOMOTIVE INDUSTRY

Building cloud native software to take drivers

Competing on Business Model

Competing on Product

Competing on Experience



FINANCIAL INDUSTRY

Building cloud native software to take customers






ENTERTAINMENT & MEDIA INDUSTRY

Building cloud native software to create and deliver content






“… the conformity between information technology structure and overall organizational context variables, including competitive strategy, is instrumental to the successful implementation of information technology systems”

Hamid Tavakolian, 1989, Linking the Information Technology Structure With Organizational Competitive Strategy



Google, Uber, Square, and venture backed start-ups operate at lightning speeds with a high level of agility Can you release new features… In minutes? Multiple times a day? Across multiple clouds? Around the world?



$4BN Financial Services

$26BN Hospitality

$50BN Transportation

$54BN Entertainment

$30BN Automotive

$3.2BN Industrial Products

CLOUD NATIVE SOFTWARE IS CHANGING

Industries



The world’s largest taxi company owns zero vehicles The world’s most popular media company creates zero content

The world’s most valuable retail company has zero inventory The world’s largest accommodation provider owns zero real estate

Source: Tom Goodwin, SVP Havas Media

CLOUD NATIVE SOFTWARE IS CHANGING

Business Models



How quickly can you react to

customer changes or

the speed of your market?

Cloud Native describes the patterns of high performing organizations delivering software faster, consistently and reliably at scale



Choosing a Cloud



Choosing the right Cloud

•  Shared Environment

•  Divided into smaller zones

•  Space can be “rented”

•  Typically bare bones/minimal groundwork

•  Additional skills/tools needed to get value




•  Shared Environment

•  Divided into smaller zones

•  Space can be “rented”

•  Typically bare bones/minimal groundwork

•  Additional skills/tools needed to get value



What is the correct cloud? How do you choose?

camellia sinensis



Is this the correct Cloud?



•  Is there a risk of lock-in? •  Do you need to bring additional tools and services?

•  Can you afford it? •  Does it make you faster?

•  Does this help add/increase technical debt




Empowered Culture

Smart Platform

Cloud Native Software

Cloud Native Application Framework



Empowered Culture

Smart Platform





How should I adopt the cloud?

VM1 VM2 VM3

VM4 VM5 VM6 •  Is this efficient? •  Is this economical? •  Is there a simpler way?

Data Access

Service

HTML JavaScript MVC

Service

Monolithic Application



Big Application Ailments

Big budgets

Gold plated with many

unused features

Slow payback of return on

investment

Source of conflict

between IT & business

Drag on business

model innovation

Expensive to change

Long release cycles & big

delays Difficult to

scale



How to write apps for the Cloud?

“In a connected system, elements are highly available to each other (via global state, for example). A modular design has connections deliberately kept to a minimum. …. During the takeoff phase, the team is constantly trying to add value by increasing the chance of survival. During the cruise phase, reducing costs adds the most value. A different mix of activities goes into achieving these different goals.”

Kent Beck August 12th, 2009 in Responsible Development, Startups



Monolith or Microservice?



What are Microservices ?

Loosely coupled service oriented architecture with bounded contexts

If every service has to be updated in concert, it’s not loosely coupled!

If you have to know about surrounding services you don’t have a bounded context.



Why Microservices? •  A Distributed System creates reusable services

•  So, it’s just like SoA - ? •  NO -> It’s SoA done right. Single function, single data domain •  Interconnectivity using common transport but stateless communication •  A microservice can run on it’s own (low coupling) and provides it’s own

business value (high cohesion) •  Anti-fragility

•  Distributed Systems with defined responsibilities are better by design: •  Individual services can be scaled separately •  Individual services can be managed in separate runtimes •  Interconnection is less rigid

•  Code can be released faster but safely



-  Managed independently

-  Not held up by slowest “train”

-  Fits cloud native “scale-up” model

-  Reduces risk

Source: Diagram from Leading the Transformation, 2015.



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,

Run Processes Port

Binding Concurrency

Disposability Dev/Prod Parity Logs Admin

Processes

Source: “The Twelve-Factor App.”



Spring IO Execution: Spring Boot

•  Convention-over-configuration, no XML, no code generation

•  Autoconfigure, embed servlet engine •  Get out of the way quickly if you want to

change defaults •  Provide production ready features •  Service Binding for Cloud Foundry •  Java, Spring, Groovy

application configuration patterns



Why Spring Boot? •  “MICRO” doesn’t mean small

•  It means to decompose •  Separate distinct components (sort, tail …..)

•  Easy to build, test and DEPLOY •  Microservices should perform one thing and perform it well •  Typically concise codebase •  Ship everything they need •  Can deployed standalone or in the cloud, singly reducing operations

overhead

It’s all about Speed and Portability!



But Microservices!



Example: Coordination Boiler Plate



•  Eureka •  Hystrix + Turbine

•  Ribbon

•  Feign

•  Zuul

http://netflix.github.io



Empowered Culture

Smart Platform



•  Microservices •  12 Factor



Cloud Native Platform



Empowered Culture

Smart Platform






The Innovation Gap in Traditional IT

Developer Operator



“The traditional model is that you take

your software to the wall that separates development and operations, and throw

it over and then forget about it.”

“Not in Amazon. You build it. You run it.”

-Werner Vogels, CTO Amazon



Platform Deliver a modern application development and operations environment that lets your developers focus on generating value for customers.

Microservices Open Source Continuous Delivery Containers DevOps


Cloud Native Power Lunch Series © Copyright 2015 Pivotal. All rights reserved.

O’Reilly and Ruxit Survey



Why Containers?



Containers?

hardware

kernel

services OS

psx App Container

resource isolation

namespace isolation

cgroups

PID Network Mount User

kz

sz

psx

VM sz

psx



Containers Pre-date the Docker Hype

Google started Linux container effort “Control

Groups”

Added to the Linux Kernel in

2007

Cloud Foundry uses Linux container

technology - “Warden

containers” early 2012

Docker is like github for container images

Docker joins Cloud Foundry

Foundation

Google, MSFT, IBM working on orchestration of multiple Docker

containers

2006 2014

Cloud Foundry has been using container technology pre-Docker

2012



What are the benefits of containers?

53

Consistent behavior Isolation = App

portability

Very lightweight

Infrastructure efficiency i.e. better density

= Agile!



Containers Alone Aren’t Enough… enter PaaS �  Orchestration & Management of Application

Instances –  Apps span multiple VMs –  Apps use multiple containers –  Dependencies with each other fail

�  Enterprise management –  Value is unlocked when standard common

services are built into each managed container



Container technology alone is not enough for enterprises

Differences -- At a Glance

Feature Warden Docker Garden PivotalCF (PaaS)

Dev Agility (Buildpacks)

Operator Agility

Multiple Levels of HA

Eco-System (Service Broker)



What does it mean to have a “Platform” ? The minimum features needed…

PaaS

Routing

Load Balancing

Service Brokers

Infrastructure automation

Log aggregation

Health monitoring &

recovery

Immutable artifact

repository



The Cloud Platform Evolution TRADITIONAL IAAS

Virtualization Platform

Operating System

Dat

abas

e

Web

/App

S

erve

r

Mes

sagi

ng

Your Application Code

Physical Servers

Dat

abas

e

Web

/App

S

erve

r

Mes

sagi

ng


IAAS


PAAS

PAAS

IAAS

CLOUD NATIVE PLATFORM



MODERN CLOUD NATIVE PLATFORM

Pivotal Cloud Foundry empowers companies with a cloud platform engineered for start-up speed—designed for continuous innovation, across multiple clouds, at scale.



ORIGINS

2013

Transferred to Pivotal from Vmware ●  Open Source ●  Cloud Native Architecture

2014

First commercialized by Pivotal ●  Pivotal Cloud Foundry (PCF) ●  Pivotal Web Services (PWS) ●  1 trillion dollars in market cap

supporting the project ●  Top talent recruited from Puppet,

AWS, Google, etc

2015

Governance passed to Cloud Foundry Foundation

2016

On 7th release of PCF

59



CLOUD FOUNDRY FOUNDATION AN OPEN INDUSTRY STANDARD

PLAT

INU

M

SILV

ER

GO

LD

60



CF OPEN SOURCE MOMENTUM

Source: http://cloud-foundry.meetup.com/ on Jun 12 2015

53 CORPORATIONS

158 MEETUPS 49 COUNTRIES

21K MEMBERS

2200 DEVELOPERS

65K COMMITS

650 CODE SUBMITTERS

SUBMITTERS

COMMITS

in

from

61


Cloud Native Power Lunch Series 62

●  Absolutely critical for CF users and ecosystem ●  Make it lasting and durable ●  CF “Core”:

○  Cloud Foundry Certified PaaS ○  Target Q4 2015

●  CF Extensions ○  Target Early 2016

CLOUD FOUNDRY CERTIFICATION PROGRAM Cloud Foundry Core •  Certified Products and “As a

Service” Implementations •  Must Use Specific CF-Release

CFF Maintained Add-ons •  Projects owned by Foundation •  Extend or work with CF Core •  Must meet qualifications for

relevant CF Extension certification

Certified CF Extensions •  Projects and products external to

the foundation •  Are certified by the foundation as

interoperable with CF Core

Extended Ecosystem •  Projects and products external to

the foundation •  Not certified

BOSH, while not in CF Core, remains critical to our ecosystem development efforts and represents several opportunities for certification programs.


Cloud Native Power Lunch Series 63

●  Financial Services ●  Industrial IoT ●  Government ●  Service Providers

CURRENT VERTICAL FOCUS

Financial Services

Industrial Internet

Service Providers

Government



PIVOTAL IS THE LEADING CONTRIBUTOR & EXPERT….

64



Everything to deploy and manage the app

APPLICATION Health management

APM

Log aggregation

Roles and Policy Security and

Isolation

Scaling

Blue green deployment



Container Scheduling

Application Framework

Services Platform Runtime

Routing Database Configuration Service Discovery

Big Data

Object Storage

Mobile

Build CI

User Provided Logging & Metrics Messaging

Circuit Breakers 12 Factor Apps RESTful Services Microservices

.NET Spring Boot Node.js Ruby on Rails

Operations Zero Downtime Deployments

Failover & Recovery Scaling Security

Patching Platform

Upgrades

Infrastructure OpenStack Amazon VMware Azure



BUILD PACKS



Platform provides standard Buildpack for runtime*

Platform provides fixed OS container image

Developer brings app

Developer brings runtime Docker image

Developer brings Docker OS image

Developer brings app

Buildpacks Docker

* Devs may also provide their own buildpacks

Platform provides fixed host OS Kernel

Platform provides fixed host OS Kernel

Application Container

Standardization or Customization is Your Choice

AND



Application Lifecycle Management: CI/CD Delivery High Quality Software, Faster and Continuously From Idea to Production

Solution: Distributed revision control and source code management. Collaborative software development

Solution: Build and test software projects continuously and incrementally. Hundreds of compatible plugins

Solution: Share binaries and manage distributions. Manage artifact lifecycle. Avoid license violations

Develop, test, QA and production on the same platform. Simple, developer friendly commands and APIs. Operational benefits for every app. Built-in ecosystem

services. Deploy, operate and scale on any IAAS

AUTOMATION. Integrate tools and automate processes from testing to builds and deployment

SPEED. Release more frequently with smaller bits will reduce complexity and improve time-to-market

QUALITY. Reduce feedback loop using test-driven development to surface problems sooner and be responsive

AGILITY. Push updates on regular basis with no downtime to improve customer experience and time to market

Commit Code Change

Automate Build & Test

(Unit Test, Static Code Analysis)

Store Binaries & Build

Artifacts

Automated Integration

Testing

Acceptance, Performance &

Load

Zero Downtime Upgrade to Production B

uild

Pip

elin

e O

pera

tions

To

ol C

hain

Gitlab Jenkins Development Test + UAT + Staging

Production

Problem: Customers want to use Git distributed source code control system, yet maintain on-premise control of it

Problem: Current application delivery pipeline is manual and error-prone, and lacks automation, scale, speed, transparency, compliance and reliability.

Problem: Development requires management of binary artifacts to incorporate 3rd party components and track application binary artifacts



Empowered Culture

Smart Platform




•  Containers •  Self-Service •  Automation •  Hybrid Cloud



Cultural Transformation



Empowered Culture

Smart Platform







Are we ready to become Cloud Native? How to organise …

"Any organization that designs a system (defined more broadly here than just information systems) will inevitably produce a design whose structure is a copy of the organization's communication structure.”

Melvyn Conway, 1968, ‘How do Committees Invent?’

“It’s managing the links between members that gets teams into trouble” J. Richard Hackman, 2009, the Edgar Pierce Professor

of Social and Organizational Psychology at Harvard University



Microservice Delivery Team

Cloud Native Platform

Micro Service

Own

Dev

QA

BA

UX

DBA

App Ops

PM



Cloud Native at Netflix “There are no longer distinct product managers, UX managers, development managers, and so on, managing downward in their silos. There is a manager for each product feature (implemented as a microservice), who supervises a team that handles all aspects of software development for the microservice, from conception through deployment.”

Adrian Cockroft, 2014, nginx.conf2014

Product Mgr UX Dev QA DBA Sys

Admin Net

Admin Storage Admin

BUSINESS CAPABILITY TEAMS USING MICROSERVICES

PLATFORM OPERATIONS TEAM

Self Service

API



Our mission is to transform how the world builds software



MODERN SOFTWARE METHODOLOGIES

A modern platform requires a modern approach to software development

3 Optimized for Change

MODERN SOFTWARE METHODOLOGY

Building a strategy for product development

Building a quality product at startup speed

An organization optimized to respond to disruption

2 Lean Startup Techniques

MODERN SOFTWARE METHODOLOGY 1 Agile Software

Methodologies

MODERN SOFTWARE METHODOLOGY



Picture of Dev Environment of the past. Fills screen. Your teams can’t look like this…



They need to look like this.



Embrace cloud platform evolution, adopt an agile development methodology, and let your developers find their voice.

Rediscover Software Development

DEPLOY DEVELOP DESIGN DEFINE



Modern Product Development

TECHNOLOGY TRANSFORMATION CULTURAL TRANSFORMATION

Cloud native application platform •  Increases developer productivity •  Unifies IT environment

•  Centralizes and enforces convention (security, scaling, etc.)

•  Generally allows developers to get back to writing code

Simple framework based on disciplined Agile practices •  Clear separation of product and

engineering roles

•  Team co-location and pair-programming •  Test –driven development and repurposing

of QA



How We Deliver Transformation

Build product with us in our office

Undergo leadership training

Take back what you’ve learned



Services for Transformation

Agile Development Product Design Product Management

Innovation Workshops Agile Immersion Discovery & Framing

Quality Assurance Data Science

Deployment



A day in the life at Pivotal Labs

https://www.youtube.com/watch?v=5h-zsDXQH_8



Empowered Culture

Smart Platform





•  Product not Project

•  Accountability •  Handle

Change



How does Pivotal Help?


Cloud Native Power Lunch Series Source: User Summit (2014)

“If you went to bed last night as an industrial company, you’re going to wake up in the morning as a software and analytics company.” - Jeff Immelt CEO, General Electric



The day Home Depot realized Amazon sold more hammers than they did, they decided to become a software company.

Source: Anecdotal



What Home Depot say about Pivotal:

https://www.youtube.com/watch?v=Bl0oH0UdJPM



Driving Digital Differentiation Pivotal Cloud Foundry and Spring Boot deliver results in 4 months d Foundry with the developer framework Spring Boot support emission control and autonomous driving initiatives from Daimler and Mercedes-Benz Cloud Foundry with the developer framework Spring Boot support emission control and autonomous driving initiatives from Daimler and Mercedes-Benz

“ With Pivotal we have minimized our innovation cycles and can now respond to changing market demands faster than ever before, both of which allowed us to develop a profound software culture in our transformational journey into a digital company… ”

- Christoph Hartung, Head of connected cars at Mercedes-Benz



Faster Time to Market

Originally Allocated 12 Software Engineers

Entire QA Team

14 months

Actually Required 6 Software Engineers

1 UX & Product Manager

6 months

Some people doubted that Pivotal’s methodology would work, but we’ve actually shown that it resulted in a faster time to market at less cost. For us, it’s been much more than a technological transformation moving to a Cloud Native Platform. It’s a new way to develop products. It’s the most exciting thing we’ve done in the last 12 months.

-Richard Leurig, SVP

“

” https://www.youtube.com/watch?v=_PWzVwytrX4 https://www.youtube.com/watch?v=qw8PLi0-QV4



We wrote the book on it.



It’s not about catching-up. Leapfrog transformation. When you learn to create software as good (or better) than Google, Uber, Square, and venture backed start-ups, and combine that with your decades of industry expertise, the question then becomes – How can Google possibly compete with you? You have the unique opportunity to become… The New Disruptor.



Silicon Valley is not a place. It’s a mindset.



PIVOTAL IS GLOBAL

This mindset is portable and Pivotal can help bring that to your organization

Palo Alto Berlin Boston Boulder Chicago Denver Dublin London

Los Angeles New York San Francisco Seattle Sydney Tokyo Toronto Washington D.C.



So …. Why Cloud Native?

•  Becoming Cloud Native can help you organise your teams in a way that improves your competitiveness

•  Moving to Cloud Native has already benefitted customers who have worked with Pivotal

•  Becoming Cloud Native improves safety and security of application processes through improved automation

•  Cloud Native allows you to focus on what’s important to your business •  Becoming Cloud Native can seem daunting, but Pivotal can help



Let’s help you become a disruptor TOGETHER



Topics in the Power Lunch Series Why Cloud Native? 18 August 2016

How to Architect & Develop Cloud Native Applications? (Part 1 & 2) 20 September & 6 October 2016

How to Modernise Legacy Applications 25 October 2016

How to enable Continuous Delivery of Software into Production 10 November

How to Operate Cloud Native Applications 6 & 20 December 2016



Q&A