Cloud-native ALMWhat every business should plan for

June 7, 2016

Neil Gehani, Sr. Product Manager, @GehaniNeil

Forward-looking statementsThis is a rolling (up to three year) roadmap and is subject to change without notice.This document contains forward looking statements regarding future operations, product development, product capabilities and availability dates. This information is subject to substantial uncertainties and is subject to change at any time without prior notification. Statements contained in this document concerning these matters only reflect Hewlett Packard Enterprise's predictions and / or expectations as of the date of this document and actual results and future plans of Hewlett Packard Enterprise may differ significantly as a result of, among other things, changes in product strategy resulting from technological, internal corporate, market and other changes. This is not a commitment to deliver any material, code or functionality and should not be relied upon in making purchasing decisions.

Hewlett Packard Enterprise confidential informationThis is a rolling (up to three year) roadmap and is subject to change without notice.

This Roadmap contains Hewlett Packard Enterprise Confidential Information. If you have a valid Confidential Disclosure Agreement with Hewlett Packard Enterprise, disclosure of the Roadmap is subject to that CDA. If not, it is subject to the following terms: for a period of three years after the date of disclosure, you may use the Roadmap solely for the purpose of evaluating purchase decisions from HP and use a reasonable standard of care to prevent disclosures. You will not disclose the contents of the Roadmap to any third party unless it becomes publically known, rightfully received by you from a third party without duty of confidentiality, or disclosed with Hewlett Packard Enterprise’s prior written approval.

Applications are changing – accelerate to a digital enterprise

4Courtesy of

Why accelerate?

– Time-to-market driving transformations– Speed - Deliver business value faster– Competitive survival

5

Feel the need for speed

Cloud-native Taxonomy

– Applications are “services” = business value– Cloud-native is a design pattern– Microservices is an architecture– Containers are portable. “If it works on my machine, it will run in production” is real– Platform to deploy “services” (PaaS)– Infrastructure to run “services (IaaS)– DevOps is a practice

7

Balancing Time Value of Money

– Time value of delivery

– Time value of shipping

8Source: Brandon Chu - Time Value of Shipping

Microservices - Reducing cycle time minimizes risk, improves quality, speed

9

VS.

Faster release cycle Less code to validate Easier to schedule

Longer test cycles

Less predictability

Unable to adapt to change

Trends enabling cloud-native

10

In the past year alone, the project has experienced a 183% increase in contributors, 515% growth in projects on GitHub, and an astounding 18,082% spike in container downloads.

- June 2015 DockerCon

Cloud applicationsFrom cloud deployed to cloud-native

AutomationMeeting economy, scaling, resiliency and velocity requirements requires

standardization and automation

Cloud DeployedCloud Aware

Cloud Native

Modern Application Requirements

© Copyright 2015 Hewlett Packard Enterprise Development LP. 2015 Restricted .The information contained herein is subject to change without notice.

Economy Scale

Velo

city

Resiliency

Value

Modern Teams - Personas and roles

13

Persona Responsibilities and rolesCollaborate in realtime through “chatops” integrations. “Bots” are members of the team

Product ManagerDefine, prioritize, measure

Create and track KPIs with analytics data coming back from releasesDefine and execute A/B tests and automatically roll back failed experimentsControl feature toggles (mobile-enabled) and measure impactDefine problems, not features; write stories

Test Engineeris (SEiT, QE)Risk mitigation in production (data-driven)

Simulate failure to test application resiliency and degradation behaviorIdentify code coverage issues based on production analyticsCreate scaling simulation tests and store test assets with codeChaos testing 24x7x365Test configuration as code, automatically triggered of any CI/CI pipeline

DevelopmentBuild, test, deploy

Track user story connection to commit, build, test and deployment artifactsIdentify vulnerable code inline and at each commitTrigger automatic testing at any point in the build to deploy cycle and in productionTrigger automatic provisioning and teardown of environments (PaaS enables)

Operations (SRE)Scalable infrastructure for automated provisioning, deploys + capacity utilization and planning

Blessing base containers; governance and securityBuild a resilient infrastructure for any developer to deployEnable a pub/sub infrastructure for data collectionProvide a standardized infrastructure for audit and compliance logs from chatops (SoT)

How software will be consumed

– Base blocks – “Extension” blocks– Disposable

Blocks Buy the blocks and assemble yourself.

How software will be buit

– On-demand– Customized solutions

– REST API– Web Hooks

Microservices – Assemble as needed to add more value to create your own solution

Scratch Programming Language: MIT

Business process

Teams should be built around business value

16

Microservices

Business activity

Conway's Law Organizations which design systems [...] are constrained to produce designs which are copies of the communication structures of these organizations

This is a bad idea

Microservice A Microservice B

API team

Business logic team

Data team

Microservice C

Best practiceFollow Conway’s Law

Data team

Business logic team

API team

Horizontal teams

…

Team A

data

Business logic

API

Microservice A

Team B

data

Business logic

API

Microservice B

Align teams to services

Path from monolith to microservices

Separate application concerns

© Copyright 2015 Hewlett Packard Enterprise Development LP. 2015 Restricted .The information contained herein is subject to change without notice.

Decoupling Monolith (legacy) to Microservice(s)

Façade Service

MonolithAdapterService

Translator Service

Monolith Domain Microservices System Domain

REST API

REST API

REST API

MicroservicesEvolution of decoupling

1990s and earlierPre-SOA

(monolithic)Tight coupling

2000sTraditional SOA Looser coupling

2010sMicroservicesDecoupled

FutureServerless

The challengeNew matrix from hell

22Courtesy of

HPE Confidential

Cloud-native Application Lifecycle Management Challenges–Plan (Track & Analyze)

– For fast cycle times - deploys n x per day– 100’s of thousands of services being built, tested, deployed, and running

–Build - automated– Programmatically trigger builds (containers) using any CI/CD– Multiple, flexible, parallel pipelines

– Test - automated– Automated - 24x7x365

– Contract (e.g API testing)– Resiliency (e.g. chaos)– Behavior (e.g. costs - containers, instances, infrastructure)

–Run– Automated deployment using Helion PaaS to any IaaS (AWS, Azure, vSphere, OpenStack)

Lifecycle Management Suite - The Revolutionary Evolution

This is a rolling (up to 3 year) roadmap and is subject to change without notice

Unified Lifecycle Suite

Plan Build Test Run

Analyze

Unified Enterprise Platform

Enterprise Agile to DevOps

SCM CIEmbedded or Connected

Deploy

Lifecycle Suite

Predictive ALM

Big ITM DataReflect Predict

Accelerate

Actionable Insights

“Speed wins in the marketplace” - Adrian Cockcroft, Netflix, Battery Ventures

–Deliver value faster

to–Capture value

faster

25

Better together

ADM + Helion Stackato

Application Lifecycle Management on multi-cloud platform

Universal Control Plane

Code EngineConcourseCI

vSphere

Cloud Foundry

Univ

ersa

l Se

rvice

Br

oker

Service catalog

ADM Services

AWSOpenStack

Web console

ALM Octane Predictive ALM Cloud-native ALMApplication Lifecycle Management

Helion Stackato (PaaS)

Future

Kubernetes

ADM Microservice

s

Docker Container Platform

IaaS

Resources

– 12-Factor Apps– Microservices – Martin Fowler– Testing Strategies in Microservices Architecture– ADM open source contributions for Cloud-native apps built as microservices

packaged in cotnainers– “Pumba” - Chaos testing inspired by Netflix simian army - open sourced– Container integration testing framework

–Published in docker’s weekly newsletter– Containerized Docker Bench security testing - open sourced

– How to reach us– Neil Gehani (PM) - @GehaniNeil

28