More Related Content Similar to Continuously Delivering Your Software on AWS - Adrian White - AWS TechShift ANZ 2018 Similar to Continuously Delivering Your Software on AWS - Adrian White - AWS TechShift ANZ 2018 (20) More from Amazon Web Services More from Amazon Web Services (20) Continuously Delivering Your Software on AWS - Adrian White - AWS TechShift ANZ 20181. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Continuously Delivering Your
Software on AWS
Adrian White, Snr Manager ISV Solutions Architecture,
Amazon Web Services
2. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. https://secure.flickr.com/photos/mgifford/4525333972
Why are we
here today?
3. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
A look back at
development at
Amazon..
https://secure.flickr.com/photos/pixelthing/15806918992/
4. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
2001
monolithic application
+
monolithic teams
5. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Monolith development lifecycle
developers
releasetestbuild
delivery pipelineapp
6. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
How do we
organize for
innovation?
» Mechanisms
Encoded behaviors that facilitate innovative thinking
» Architecture
Structure that supports rapid growth and change
» Culture
Customer obsession, hire builders, let them build,
support them with a belief system
» Organization
Small, empowered teams that own what they create
7. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
• Single-purpose
• Connect only through
APIs
• Connect over HTTPS
• Largely “black boxes” to
each other
• “Microservices”
8. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Monolithic vs. SOA vs. Microservices
SOA
Coarse-
grained
Microservices
Fine-grained
Monolithic
Single Unit
9. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Microservices:
• Many very small components
• Business logic lives inside of
single service domain
• Simple wire protocols(HTTP
with XML/JSON)
• API driven with SDKs/Clients
SOA:
• Fewer more sophisticated
components
• Business logic can live across
domains
• Enterprise Service Bus like
layers between services
• Middleware
Microservices vs. SOA
9
10. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
• Two-pizza teams
• Full ownership
• Full accountability
• Aligned incentives
• “DevOps”
11. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What is DevOps?
Cultural
Philosophy
Practices Tools
12. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
How do Two Pizza Teams work?
• We call them “Service teams”
• Own the “primitives” they build:
• Product planning (roadmap)
• Development work
• Operational/Client support work
• “You build it, you run it”
• Part of a larger concentrated org (Amazon.com, AWS,
Prime, etc)
• Have a P&L
13. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Who Does
QA?
The Two
Pizza
Team
14. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Who Does
On Call?
The Two
Pizza
Team
15. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What does
Ops Do?
Not
Exist
16. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What about Ops/QA/Etc?
Everyone exists on a “service team” focused on their primitive(s):
• SDE’s focused on developing
• - SDM one manager per team
• PM’s focused on product direction
• TPM’s help drive development
• SE’s focused on infra/tooling
• SDET’s focused on test excellence throughout the organization
Some folks are shared across the org, some on individual teams
Most ”2 pizza” teams are just
these 3 roles
17. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Boy, that sounds like a lot of freedom?
It is! Teams are empowered and also held to high
standards:
• Thorough onboarding/training
• Patterns/practices defined at scale and with 20+
years of organizational knowledge
• Regular technical and business metric reviews
• Regular sharing of new tools, services, technologies,
etc, by internal subject matter experts
• Public sharing of COEs; “Correction of Errors” our
post-mortem process/tool
17
18. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Shared Mechanisms
PR/FAQ 6 Pagers Working
Backwards
WBRs COE OP1/OP2
19. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Weekly Business Review (WBR)
• 4-box/2x2 review
• Single sheet of paper, 4 box grid:
• Past week’s business trends
• Risks/Issues/Challenges
• Goals
• Upcoming launches
• Operational dashboards
20. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
OP1/OP2
• Teams will write OP1 documents every year to plan the following year’s plans.
• Anyone on a team can suggest items to go onto OP1
• Typically includes state of the business, highlights/lowlights, YTD Wins,
customer feedback snippets, “think big” ideas, HC/Funding requests, cross team
initiatives, lots of areas to be “vocally self critical”
• Start at the 2-pizza team level and then get aggregated up through GM/Dir of
space level
• Typically reviewed/signed-off on in August
• Not unusual to go through more than 1 round of senior review
• Requires Andy Jassy level sign off at the end of the day
• OP2 is then written at the end of the year as a review of the previous year and
to offer tweaks/adjustments to OP1’s outcome.
21. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Missing tools
developers delivery pipelineservices
???
22. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
• Self-service
• Technology-agnostic
• Encourage best
practices
• Single-purpose
services
23. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
• Deployment service
• No downtime
deployments
• Health checking
• Versioned artifacts
and rollbacks
24. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Things went much
better under this
model and teams were
developing features
faster than ever, but
we felt that we could
still improve.
25. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Every year we run an internal
“tech survey” of all technical
employees at Amazon. In
2009, the study found that
many teams felt they were
still being slowed down by
manual processes and work
flows.
This led us to build..
26. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Pipelines Automated actions and
transitions; from check-in to
production
Development benefits:
• Faster
• Safer
• Consistent &
Standardized
• Visualization of the
process
27. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
In 2014 our yearly
technical survey results
found only one
development tool/service
could be correlated
statistically with happier
developers:
Our pipelines service!
28. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
continuous delivery
==
happier developers!
https://www.flickr.com/photos/cannnela/4614340819
29. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
2 Pizza Team Responsibility Venn Diagram
Responsible for
THEIR
PRODUCT
Deployment tools
CI/CD tools
Monitoring tools
Metrics tool
Logging tools
APM tools
Infrastructure
provisioning tools
Security tools
Database management
tools
Testing tools
….
Not responsible for
*
*Unless their product belongs in the blue
30. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Microservice development lifecycle
developers delivery pipelinesservices
releasetestbuild
releasetestbuild
releasetestbuild
releasetestbuild
releasetestbuild
releasetestbuild
31. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
> 60 million deployments a year*
Thousands of teams
× Microservice architecture
× Continuous delivery
× Multiple environments
*2016 number
32. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
The Future
33. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
2 Pizza Team Responsibility Venn Diagram
Responsible for Not responsible for
*
NOT
THEIR
PRODUCT
*Unless their product belongs in the blue
Application development
Infrastructure
management
Application configuration
Pipeline configuration
Alarms
Runbooks
Testing
Compliance
Roadmap tracking
Goals tracking
On-call
Support escalation
….
34. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Determining the right balance
The more time spent on operational tasks, the
less time spent on development tasks
35. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Determining the right balance
Teams aim to spend <20% of their time on non-
development tasks
The more time spent on operational tasks, the
less time spent on development tasks
36. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
2 Pizza Team Responsibility Venn Diagram
Responsible for
THEIR
PRODUCT
Not responsible for
NOT
THEIR
PRODUCT
Can we shift more from a
team’s responsibility to the
platform/shared services?
37. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
No server is easier to manage than
"no server”.
Dr. Werner Vogels
Amazon CTO
38. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Serverless means…
No servers to provision
or manage
Scales with usage
Never pay for idle Availability and fault
tolerance built in
39. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Serverless applications
SERVICES (ANYTHING)
Changes in
data state
Requests to
endpoints
Changes in
resource state
EVENT SOURCE FUNCTION
Node.js
Python
Java
C#
Go
40. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Components of a serverless application
• Low/zero administrative overhead
• Instant scalability or easy to tune knobs
• Pricing directly aligned with usage
• High availability/redundancy built in
• Multi-region or multi-account patterns well defined
• All are PCI and HIPAA eligible services
AWS
Lambda
Amazon
S3
Amazon
CloudFront
Amazon
DynamoDB
Amazon
Kinesis
Streams
Amazon
Cognito
Amazon API
Gateway
Amazon
SNS
41. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
42. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What would it take for your team to build the
backend for these products yourself?
• Amazon API Gateway
• Amazon Kinesis Video
Streams
• Amazon Rekognition Video
• AWS Lambda
• Amazon S3
• Amazon DynamoDB
• Amazon Cognito
• AWS Step Functions
• Amazon SageMaker
• Amazon Machine
Learning
On AWS:
43. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What would it take for your team to build the
backend for these products yourself?
• Amazon API Gateway
• Amazon Kinesis Video
Streams
• Amazon Rekognition Video
• AWS Lambda
• Amazon S3
• Amazon DynamoDB
• Amazon Cognito
• AWS Step Functions
• Amazon SageMaker
• Amazon Machine
Learning
On AWS:
The only one of these you’d
provide your own code for is
Lambda.
44. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
How does serverless
help with
development?
https://www.flickr.com/photos/lachlanhardy/415083
45. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Deep dive on a typical ‘service’
1 per Availability Zone
1 vCPU, 1GB RAM
~2048 LoC
46. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Gilt’s Story:
1 per Availability Zone
1 vCPU, 1GB RAM
~2048 LoC
THIS IS BASICALLY A
LAMBDA FUNCTION!
47. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Lines of Code (LoC)
Monolith = 10,000s to 1,000,000s
Microservices = 100s to 1000s
Lambda “nano-services” = 10s to 100s
48. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Lines of Code (LoC)
Monolith = 10,000s to 1,000,000s
Microservices = 100s to 1000s
Lambda “nano-services” = 10s to 100s
+ Simplified testing of code
+ Easier to onboard new developers
+ Super fast deployment times
+ Orchestration in managed services not code
+ Reduced “blast radius” of issues
+ Greatly reduced technical debt
49. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What happens if we
reduce operational
burden massively and
reduce the amount of
code we have to write?
50. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What if 2 pizzas
is 1 too many?
51. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
× Microservice architecture
× Continuous delivery
× Multiple environments
Thousands of teams
> XXX million deployments a year?
If fewer people are needed to
build things, can we build
more things & faster???
?x more
52. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
<2 Pizza Team Model Potential Benefits
• Smaller getting started headcount for a new team
• Lower cost of experimentation for new ideas
• Even less drift between teams in terms of operating
procedures (more standards?)
• Greater agility/time to market
• Increased availability
• Reduced technical debt over time
53. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS Code* Services
AWS CodePipeline AWS CodeDeploy AWS CodeCommit AWS CodeBuild
54. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Source Build Test Production
AWS CodeCommit
Tool alignment with software release steps:
D E V L O U N G E
AWS Code Services
55. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS CodeBuild
D E V L O U N G E
Tool alignment with software release steps:
AWS Code Services
Source Build Test Production
56. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Third Party
Tooling
D E V L O U N G E
Tool alignment with software release steps:
AWS Code Services
Source Build Test Production
57. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS CodeDeploy
D E V L O U N G E
Tool alignment with software release steps:
AWS Code Services
Source Build Test Production
58. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Third Party
Tooling
AWS CodeCommit AWS CodeBuild AWS CodeDeploy
AWS CodePipeline D E V L O U N G E
Tool alignment with software release steps:
AWS Code Services
Source Build Test Production
59. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Third Party
Tooling
AWS CodeCommit AWS CodeBuild AWS CodeDeploy
AWS CodePipeline
AWS CodeStar
Tool alignment with software release steps:
AWS Code Services
Source Build Test Production
60. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
• DevOps and AWS
• https://aws.amazon.com/devops/
• AWS Developer Centre
• https://aws.amazon.com/developer/
• Get started with AWS CodeStar at:
• https://console.aws.amazon.com/codestar
• Learn more at:
• https://aws.amazon.com/codestar
More information
Let’s Build!
61. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Enablement Training
2 Day Workshop
Checkpoints
Account Manager & Solution Architect,
Account Plan, Opportunity Review
ISV Deliverables
Multi-tenanted Architecture
2 x AWS Professional Certifications
AWS Deliverables
Sandbox Credits ($20k), Summit or
re:Invent sponsorship, This is My
Architecture & Solution Space listing
SaaS
Enablement Training
2 Day Workshop
Checkpoints
Monthly Office Hours, Deep Drive
Architecture sessions & Roadmap
Sharing, Opportunity Review
ISV Deliverables
Scalable Self Healing Architecture
2 x AWS Associate & 1 DevOps
Certifications
AWS Deliverables
Sandbox Credits ($10k), GTM Plan, MDF
($20k) & Partner Connections
Modernize
Enablement Training
1 Day Workshop
Checkpoints
Virtual Fortnightly Office Hours
ISV Deliverables
Replatformed High Availability
Architecture (QuickStart or Marketplace
Listing), Technical Essentials
AWS Deliverables
Sandbox Credits ($10k), Well Architected
Review, Demo Day
Timeframe: 3 Months
Migrate
Timeframe: 6 Months
Timeframe: 1 Year
AWS TechShift Accelerator
Sydney 5th February 2019
Melbourne 7th February 2019
Sydney 14-15th May 2019
Melbourne 16-17th May 2019
Register Your Interest: https://aws.amazon.com/events/techshift/accelerator/
62. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
GET TRAINED AND CERTIFIED ON AWS
Benefits to APN Partners:
• Free Digital Training, including AWS Cloud
Practitioner Essentials
• Online Accreditation Training courses to
learn at your own pace
• ILT and vILT sessions of our Solutions
Training for Partners (STP) courses
• Discounted Classroom Training for APN
Partners
• AWS Credits available when achieving AWS
Certification (all Partner Tiers)
Next steps:
1. Enroll now! aws.training
2. Talk to your Account Manager or Partner Development team (aws-anz-pdr@amazon.com) for more
details!
63. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Thank you.
whiteadr@amazon.com