1.
Cloud-native ALM
What every business should plan
for
June 7, 2016
Neil Gehani, Sr. Product Manager, @GehaniNeil

2.
Forward-looking statements
This 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.

3.
Hewlett Packard Enterprise confidential information
This 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.

4.
Applications are changing – accelerate to a digital enterprise
4
Courtesy of

5.
Why accelerate?
– Time-to-market driving transformations
– Speed - Deliver business value faster
– Competitive survival
5

6.
Feel the need for speed

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

8.
Balancing Time Value of Money
– Time value of delivery
– Time value of shipping
8
Source: Brandon Chu - Time Value of Shipping

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

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

11.
Cloud applications
From cloud deployed to cloud-native
Automation
Meeting economy, scaling, resiliency and velocity requirements requires standardization
and automation
Cloud Deployed
Cloud Aware
Cloud Native

12.
Modern Application Requirements
© Copyright 2015 Hewlett Packard Enterprise Development LP. 2015 Restricted .The information contained herein is subject to change without notice.
Economy Scale
VelocityResiliency
Value

13.
Modern Teams - Personas and roles
13
Persona Responsibilities and roles
Collaborate in realtime through “chatops” integrations. “Bots” are members of the
team
Product Manager
Define, prioritize, measure
Create and track KPIs with analytics data coming back from releases
Define and execute A/B tests and automatically roll back failed experiments
Control feature toggles (mobile-enabled) and measure impact
Define problems, not features; write stories
Test Engineeris (SEiT, QE)
Risk mitigation in production (data-driven)
driven)
Simulate failure to test application resiliency and degradation behavior
Identify code coverage issues based on production analytics
Create scaling simulation tests and store test assets with code
Chaos testing 24x7x365
Test configuration as code, automatically triggered of any CI/CI pipeline
Development
Build, test, deploy
Track user story connection to commit, build, test and deployment artifacts
Identify vulnerable code inline and at each commit
Trigger automatic testing at any point in the build to deploy cycle and in production
Trigger automatic provisioning and teardown of environments (PaaS enables)
Operations (SRE)
Scalable infrastructure for automated
provisioning, deploys + capacity utilization
utilization and planning
Blessing base containers; governance and security
Build a resilient infrastructure for any developer to deploy
Enable a pub/sub infrastructure for data collection
Provide a standardized infrastructure for audit and compliance logs from chatops
(SoT)

14.
How software will be consumed
– Base blocks
– “Extension” blocks
– Disposable
Blocks Buy the blocks and assemble yourself.

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

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

17.
This is a bad idea
Microservice A Microservice B
API team
Business logic team
Data team
Microservice C

18.
Best practice
Follow 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

19.
Path from monolith to microservices
Separate application concerns

20.
© 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
Monolith
Adapter
Service
Translator
Service
Monolith Domain Microservices System Domain
REST API
REST API
REST API

21.
Microservices
Evolution of decoupling
1990s and earlier
Pre-SOA (monolithic)
Tight coupling
2000s
Traditional SOA
Looser coupling
2010s
Microservices
Decoupled
Future
Serverless

22.
The challenge
New matrix from hell
22
Courtesy of

23.
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)

24.
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 CI
Embedded or Connected
Deploy
Lifecycle Suite
Predictive ALM
Big ITM Data
Reflect Predict
Accelerat
e
Actionable Insights

25.
“Speed wins in the marketplace” - Adrian Cockcroft, Netflix, Battery
Ventures
–Deliver value
faster
to
–Capture value
faster
25

26.
Better together
ADM + Helion Stackato

27.
Application Lifecycle Management on multi-cloud platform
Universal Control Plane
Code Engine
ConcourseCI
vSphere
Cloud
Foundry
Universal
Service
Broker
Service catalog
ADM Services
AWSOpenStack
Web console
ALM Octane Predictive ALM Cloud-native ALM
Application Lifecycle Management
Helion Stackato (PaaS)
Future
Kubernetes
ADM
Microservices
Docker Container Platform
IaaS

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