AWS Marketplace DevOps Workshop Series Module 1 Slides

AWS Marketplace DevOps Workshop Series
Module 1: Practicing DevOps

Helen Beal
Chief Ambassador, DevOps Institute
Helenjbeal
@bealhelen
Dr. James Bland

Global Tech Lead - DevOps at AWS
jamesbland123
Helen Beal
Chief Ambassador, DevOps Institute
helenjbeal
@bealhelen
About DevOps Institute
DevOps Institute’s mission is to advance the
human elements of DevOps by creating a safe
and interactive environment where our
members can network, gain knowledge, grow
their careers, support enterprise transformation
and celebrate professional achievements.
We connect and enable the global DevOps

community to drive change in the digital age. Become a professional member at
www.devopsinstitute.com
Helen Beal
MISSION: Bringing Joy to Work
Herder of Humans
@bealhelen
Helen Beal is a DevOps and Ways of Working

coach, Chief Ambassador at DevOps Institute and
an ambassador for the Continuous Delivery
Foundation. She is the Chair of the Value Stream
Management Consortium and provides strategic
advisory services to DevOps industry leaders
such as Plutora and Moogsoft. She is also an
analyst at Accelerated Strategies Group. She
hosts the Day-to-Day DevOps webinar series for
BrightTalk, speaks regularly on DevOps topics, is
a DevOps editor for InfoQ and also writes for a
number of other online platforms. She regularly
appears in TechBeacon’s DevOps Top100 lists
and was recognized as the Top DevOps
Evangelist 2020 in the DevOps Dozen awards.
You will learn:
- How DevOps influences organizational, team and
system design in cloud
- Why value stream centric thinking is essential to
Flow: Talk Map -

achieve continuous compliance
How CICD and DevOps toolchains accelerate value
outcomes and support safety engineering
CALMS
The
Frameworks Three
Ways
What a
DevOps
Digital DevOps DevOps CICD Journey
Disruption Principles Practices Looks Like
New DevOps
ways of Toolchains
working
Digital Disruption
The 5th Technology Revolution
• Enterprises have young, nimble start-up To meet these

competitors changing
• Agile software development and cloud conditions, IT
infrastructure is increasing must adapt its
• IT can no longer operate in a silo culture culture,
• More organizations are migrating to the cloud practices and
• Consumers have “app” mentalities and automation to
expectations be more
• There is more data available to the business ‘continuous’.
• Time to value must accelerate
Carlota Perez
1 2 3 4 5
The The age Age of steel, Age of oil, Age of

industrial of steam electricity automobiles information
revolution and and heavy and mass and
railways engineering production telecomms
1771 1829 1875 1908 1971
Icons made by Freepik and Eucalyp from www.flaticon.com

World Economic Forum
1 2 3 4 5
Steel, oil, Digital AI, big data, Connection of

Steam electricity, revolution frontier tech
robotics,
engines combustio to purpose
IoT,
n engines blockchain and inclusivity
and crypto
18th -19th 1870-1914 1980’s 21st 21st
century Century Century
Icons made by Freepik, Goodware and Eucalyp from www.flaticon.com

New Ways of Working
Better, sooner, faster, safer, happier
Dimension Traditional IT DevOps

Batch size Large & Monolithic Micro & Loosely Coupled
Organization Skill Centric Silos Autonomous squads
Scheduling Centralized Decentralized & Continuous
Release High Risk Event “Like Breathing”
Information Disseminated Actionable
Culture Do Not Fail Fail Early
Metric Cost & Capacity Flow
‘Definition of Done’ “I did my job.” “The customer has received value”
Adapted from an original article by Mustafa Kapadia

Check-in with James
How does cloud help us

with these transitions?
Frameworks
The DevOps Superpattern, the harmonious and polygamous marriage
VSM
lean learning
organizations
agile DEVOPS safety

culture
ITSM DevSecOps SRE

Check-in with James
Where were you when you

discovered DevOps?
CALMS
An elevator acronym to describe DevOps
C CULTURE
John Willis
A AUTOMATION
L LEAN Damon Edwards
M MEASUREMENT
Jez Humble
S SHARING
Culture Automation Lean Measurement Sharing
Organizational Goal is to be high Focus is on the High level goals Transparency and
purpose has clarity performing IT and customer linked to PBIs clarity throughout
organization the organization
Authority is Loosely coupled Value stream Teams measure Teams reward

distributed, teams systems centric thinking themselves each other for
have autonomy collaboration
Failure is a learning ‘Shift left’, fast Focus is on Data driven Stories are shared
opportunity feedback removing waste decision making - good AND bad
Leaders are Observability leads Work is visible Measurements Leaders do not

transformational to discovery leads used to drive punish failure but
to improvement experiments to globalize local
inspect and adapt learnings
Transformational Leadership
Distributing authority, breaking down silos: “We build it, we own it”
"The goal of leadership is not to

command, control, berate, intimidate, and
evaluate workers through some set of
contrived metrics. Instead, the job of
leaders is to help organizations become
better at self-diagnosis, self-improvement,
and to make sure that local discoveries
can be translated and converted to global
improvements.”
Dr Stephen Spear cited by Gene Kim

The characteristics of transformational leadership in Beyond the Phoenix Project
are highly correlated with IT performance and employee Net
Promoter Score (eNPS).
From The State of DevOps Report 2017
Check-in with James
“You build it, you run it”

originated with Werner
Vogels. Let’s talk about it!
The Three Ways
Key principles of DevOps as featured in The Phoenix Project
The First Way The Second Way The Third Way

Continuous Experimentation
Flow Feedback
& Learning
Understand and increase the Create short feedback loops Create a culture that fosters:
flow of work (left to right) that enable continuous • Experimentation, taking risks
improvement (right to left) and learning from failure
• Understanding that
repetition and practice is the
prerequisite to mastery
The Five Ideals
As featured in The Unicorn Project
The First Ideal Locality and Simplicity
The Second Ideal Focus, Flow, and Joy
The Third Ideal Improvement of Daily Work
The Fourth Ideal Psychological Safety
The Fifth Ideal Customer Focus

DevOps Practices
All the continuouses
Continuous Learning
Continuous Improvement
Continuous Funding
Sublime
Continuous
Testing
Continuous
Integration
Continuous
Delivery
Continuous
Deployment
customer
experience
Continuous Compliance
Continuous Intelligence
CICD
"In short, CI/CD toolchains help
with velocity and quality of
code, allow for better
collaboration among the
teams and automates many
steps, tasks and processes
which reduced the risk and
cost of software
development."
Continuous Integration
You can do this in waterfall too… if you want to
● All developers check code in at least daily to trunk

o Trunk based development
Each check-in is validated by
●
o An automated build
Avoid
o Automated unit, integration and acceptance tests ‘merge
● Is dependent on consistent coding standards
● Requires version control repositories and CI servers to hell’
collect, build and test committed code together
● Runs on production-like environments
● Allows for early detection and quick remediation of
errors from code changes before moving to production
Continuous Delivery
Software is always in a releasable state - ready to go, at the push of a button
● Takes continuous integration to the next

level
● Provides fast, automated feedback on a
system’s production-readiness
● Prioritizes keeping software
releasable/deployable over working on new
features
● Relies on a deployment pipeline that enables
push-button deployments on demand
● Reduces the cost, time, and risk of delivering
incremental changes
Continuous Delivery
Leads to higher organizational performance
Continuous Deployment
Continuous Delivery
Integration Acceptance
Dev Unit Test Production
Test Test
Manual Automatic
trigger trigger
Continuous Deployment
Integration Acceptance
Dev Unit Test Production
Test Test
The Deployment Pipeline
DevOps Toolchains
The Value Cycle
INSIGHTS AND ANALYSIS PORTFOLIO AND BACKLOG
Monitoring and observability provide Vision and goals are set and
insights into customer reaction to aligned to epics, features, PBIs
changes and report on value and user stories.
realization.
The Value
Cycle CONTINUOUS
CONTINUOUS INTEGRATION
DELIVERY
Code is created, artifacts
The changes are incorporated, versions
approved, released and controlled, code is built in a
operated in the live trunk-based manner.
environment.
CONTINUOUS TESTING
Functional and non-functional

testing takes place at every
commit at every step or gate
through route to live.
Portfolio Management
realization.
The DevOps
Toolchain CONTINUOUS
DELIVERY
environment.
CONTINUOUS TESTING

Product Backlog
realization.
The DevOps
DELIVERY
environment.
CONTINUOUS TESTING

Planning
realization.
The DevOps
DELIVERY
environment.
CONTINUOUS TESTING

Artifact Repository
realization.
The DevOps
DELIVERY
environment.
CONTINUOUS TESTING

Version/Source Control
realization.
The DevOps
DELIVERY
environment.
CONTINUOUS TESTING

CI Server
realization.
The DevOps
DELIVERY
environment.
CONTINUOUS TESTING

Unit Testing
realization.
The DevOps
DELIVERY
environment.
CONTINUOUS TESTING

Integration Testing
realization.
The DevOps
DELIVERY
environment.
CONTINUOUS TESTING

User Acceptance Testing
realization.
The DevOps
DELIVERY
environment.
CONTINUOUS TESTING

Security Testing
realization.
The DevOps
DELIVERY
environment.
CONTINUOUS TESTING

Environment Orchestration
realization.
The DevOps
DELIVERY
environment.
CONTINUOUS TESTING

Service Desk
realization.
The DevOps
DELIVERY
environment.
CONTINUOUS TESTING

Logging and Monitoring
realization.
The DevOps
DELIVERY
environment.
CONTINUOUS TESTING

AIOps
realization.
The DevOps
DELIVERY
environment.
CONTINUOUS TESTING

Observability
realization.
The DevOps
DELIVERY
environment.
CONTINUOUS TESTING

Value Stream Management Platform
INSIGHTS
Inspect real-time data AND ANALYSIS Connect
PORTFOLIO AND BACKLOG planning to
and adapt delivery
realization.
Gain insights into Value Stream Visibility into cross

waste; optimize flow value stream changes
Management CONTINUOUS
DELIVERY
environment.
Manage dependencies Trace user stories as

while you break them CONTINUOUS TESTING they travel

commit at everycompliance
Continuous step or gate
Check-in with James
How does the DevOps

toolchain look
different in cloud?
What a DevOps Journey Looks Like
J-Curve of Transformation - 2018 State of DevOps Report
Key Takeaways
DevOps = Better, faster, safer, sooner, happier
Continuousness CALMS DevOps + Cloud
● Continuous testing ● Cloud tech correlates to DevOps

● Continuous integration
● Culture and organizational performance
● Continuous delivery ● Automation ● Cloud solves common DevOps
● Continuous deployment problems:
● Continuous improvement ● Lean ○ Production-like test
● Continuous compliance environments
● Continuous intelligence
● Measurement ○ Loosely coupled services
● Continuous funding... ● Sharing ○ Integrated toolchains
Dr. James Bland
Global Tech Lead - DevOps at AWS
Jamesbland123
Amazon’s journey
Just starting out
This is how many web

architectures started out, and it
is how Amazon started too…
There any many bottlenecks,

and scaling of the web server
was an immediate factor
© 2021, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Scaling v1
This was a bit better,

still not very scalable
Challenges
• Dependencies on other teams

• Communication
• Speed of innovation
• Deployment risk
Our mission
Our task was to improve: What we did:

• Innovation • Decomposed for agility
• Speed • Cultural and operational
• Agility shift
• Safety • Created tools for software
• Team Dynamics delivery
Going further
Principles
• Make units as small as possible
(Primitives)
• De-couple based on scaling
factors,
not functions
• Each service operates
independently
“Communication is terrible!” —
Jeff Bezos
• APIs (contracts) between services
Impact to our development
Monolith development lifecycle
Developers Services
Delivery pipelines
Build Test Release Monitor
Developers Services
Delivery pipelines
This led to changes in organization
Developers Services
Impact to our organization
Getting (re)organized
“Two-pizza” teams
• Own a service
• Minimizes social constraints
(Conway’s law)
• Autonomy to make decisions
Transformation timeline
2001 2002
Monolithic Microservices
application + teams + 2-pizza teams
Teams own everything
• Planning • Operation
• Security • Bugs
• Performance • Documentation
• Scalability • Testing…
• Deployment
1. Building Blocks
2. Guardrails
Guardrails are mechanisms, such

What are
as processes or practices, that
guardrails? reduce both the occurrence &
blast radius of undesirable
application behavior
What are some real-world guardrails?
Monitoring Provisioning Deployment Cost Security

management & compliance
CPU Utilization Access Time window Resource Account set
Database permissions Toolsets available costs up/access
throughput Resource Resource Standards
Size or timing of utilization
Business availability test releases compliance
Spend run rates
processes Configuration Certificate
maintenance
3. Fully Automated Deployments
Source Build Test Production
• Check-in source code • Compile code • Integration tests with • Deploy to production
such as .java files and • Unit tests other systems environments
Dockerfile • Style checkers • Load testing • Monitor code in
• Peer review new code • Create container • UI tests production in order to
images • Security testing quickly detect errors
Amazon Continuous Delivery: Deep Dive
Source
Source Build
Source Build alpha
Automated
tests
Pre-production
Source Build alpha beta
Automated Automated
tests integration
tests
Automated
load/perf
tests
Automated
browser
tests
Pre-production
Source Build alpha beta gamma
Automated Automated Automated

tests integration integration
tests tests
Automated Automated
load/perf synthetic
tests tests
Automated API smoke

browser tests
tests
Pre-production

tests tests
Automated Automated
load/perf synthetic
tests tests
Automated API smoke

browser tests
tests
Pre-production Production

tests tests
Automated Automated
load/perf synthetic
tests tests
Automated API smoke

browser tests
tests

tests tests
Automated Automated
load/perf synthetic
tests tests
Automated API smoke

browser tests
tests
Automated Automated Automated Synthetic

tests integration integration Monitoring
tests tests
Automated Automated
load/perf synthetic
tests tests
Automated API smoke

browser tests
tests
Automated Automated Automated Synthetic Synthetic

tests integration integration Monitoring Monitoring
tests tests
Automated Automated
load/perf synthetic
tests tests
Automated API smoke

browser tests
tests

tests tests
Automated Automated
load/perf synthetic
tests tests
Automated API smoke Synthetic

browser tests Monitoring
tests

tests tests
Automated Automated …
load/perf synthetic
tests tests

browser tests Monitoring
tests
App code Automated Automated Automated Synthetic Synthetic

tests tests
Infrastructure
as code
Automated Automated …
load/perf synthetic
tests tests
OS patching

Configuration browser tests Monitoring
tests
Now we have…
Modern applications
Today we have modern applications
• Use independently • Scale globally

scalable microservices • Are fault tolerant
(serverless, • Carefully mange state
containers...) and persistence
• Connect through APIs • Have security built-in
• Deliver updates
continuously
• Adapt quickly to change
Deployment at scale
1,000s Micro-
CI/CD Env. 190 Million
= Deployments/Year
of teams services
Just the beginning
Along the way we have learned a lot about writing software

That’s performant, safe, and scalable
We have had to solve some really hard problems
At massive scale
We know our way is not the only way, and many of our solutions are
not fancy
But we know they work
We are long obsessed with building things to help our customers
We want to share the benefits of what we learned along the way
The Amazon Builders’ Library
McDonald’s brings home delivery to market
in four months
“This was a four month-duration for us—

from idea, to development to massive
scale. That's the new norm that we see
everyday.”
- Thilina Gunasinghe, Chief Technology Architect, McDonald’s
Scalability and reliability to Multi-country support, each Cost sensitive – selling

deliver over 1 million orders with multiple delivery partners hamburgers!
per hour
DevOps tooling is critically important for successful practices
The DevOps
Toolchain
8,000+ 1,600+ 24 290,000+ 1.5M+
listings ISVs regions customers subscriptions
AWS Marketplace DevOps Workshop Series participating partner hands-on labs
And more coming soon!
Next steps
Bookmark the Workshop Series landing page, check back for new content or
subscribe to email updates
Move on to Module 2: CI/CD Pipelines and get hands-on with labs
Visit the AWS Marketplace website to experiment with DevOps tooling
Move on to Module 2: CI/CD Pipelines
https://pages.awscloud.com/awsmp-h2-dev-aws-marketplace-devops-workshop-series.html

AWS Marketplace DevOps Workshop Series Module 1 Slides

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AWS Marketplace DevOps Workshop Series Module 1 Slides

Uploaded by

Copyright:

Available Formats

AWS Marketplace DevOps Workshop Series

Module 1: Practicing DevOps

Dr. James Bland

We connect and enable the global DevOps

Helen Beal is a DevOps and Ways of Working

Flow: Talk Map -

• Enterprises have young, nimble start-up To meet these

The The age Age of steel, Age of oil, Age of

1771 1829 1875 1908 1971

Icons made by Freepik and Eucalyp from www.flaticon.com

Steel, oil, Digital AI, big data, Connection of

Icons made by Freepik, Goodware and Eucalyp from www.flaticon.com

Dimension Traditional IT DevOps

Adapted from an original article by Mustafa Kapadia

How does cloud help us

agile DEVOPS safety

ITSM DevSecOps SRE

Where were you when you

L LEAN Damon Edwards

Authority is Loosely coupled Value stream Teams measure Teams reward

Leaders are Observability leads Work is visible Measurements Leaders do not

"The goal of leadership is not to

Dr Stephen Spear cited by Gene Kim

“You build it, you run it”

The First Way The Second Way The Third Way

The First Ideal Locality and Simplicity

The Second Ideal Focus, Flow, and Joy

The Third Ideal Improvement of Daily Work

The Fourth Ideal Psychological Safety

The Fifth Ideal Customer Focus

● All developers check code in at least daily to trunk

● Takes continuous integration to the next

Functional and non-functional

Functional and non-functional

Functional and non-functional

Functional and non-functional

Functional and non-functional

Functional and non-functional

Functional and non-functional

Functional and non-functional

Functional and non-functional

Functional and non-functional

Functional and non-functional

Functional and non-functional

Functional and non-functional

Functional and non-functional

Functional and non-functional

Functional and non-functional

Gain insights into Value Stream Visibility into cross

Manage dependencies Trace user stories as

Functional and non-functional

How does the DevOps

Continuousness CALMS DevOps + Cloud

● Continuous testing ● Cloud tech correlates to DevOps

This is how many web

There any many bottlenecks,

This was a bit better,

• Dependencies on other teams

Our task was to improve: What we did:

Build Test Release Monitor

Build Test Release Monitor

Build Test Release Monitor

Build Test Release Monitor