How AWS builds Serverless services using Serverless

Development transformation at Amazon: 1994-2001 monolithic architecture + hierarchical organization © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. 2002+ decoupled services + 2 pizza teams

2 Pizza Team Responsibility Venn Diagram THEIR PRODUCT Responsible for © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. * 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

Pipelines Automated actions and transitions; from check-in to production Development benefits: • Faster • Safer • Consistent & Standardized • Visualization of the process © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

Thousands of teams × Microservice architecture × Continuous delivery × Multiple environments

60 million deployments a year* *2016 number © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

2 Pizza Team Responsibility Venn Diagram Application development Infrastructure management Application configuration Pipeline configuration Alarms Runbooks Testing Compliance Roadmap tracking Goals tracking On-call Support escalation …. Responsible for © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. * NOT THEIR PRODUCT Not responsible for *Unless their product belongs in the blue

Quick poll! How many of you run in 7 or fewer AWS Regions? How many of you run in 5 or fewer AWS Regions? How many of you run in just 2 AWS Regions? How many of you run in just 1 AWS Region? © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

2 Pizza Team Responsibility Venn Diagram Can we shift more from a NOTto the team’s responsibility THEIR THEIR platform/shared services? PRODUCT PRODUCT Responsible for © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Not responsible for

From the earliest days of AWS Lambda we saw lots of repeatable patterns (internally and externally) © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Photo by Kristian Strand on Unsplash

AWS Serverless Application Repository API © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/serverlessrepo.html

Auth Lambda SDK API API Lambda Auth Lambda Search API Assets Bucket Entity/View Tables API Lambda Search Domain © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Async Processing Lambdas

Not seen • Async processing Lambdas interfacing with Amazon SNS/Amazon SQS • A few other internal services • Alpha/beta/gamma • Multiple regions © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

Not seen • Async processing Lambdas interfacing with Amazon SNS/Amazon SQS • A few other internal services • Alpha/beta/gamma • Multiple regions • A single Amazon EC2 instance per region, to test that the service is working properly BEST PRACTICE ALERT: Don’t test from the managed service to managed service to be tested © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

Building with Serverless services at AWS • • • • • Using Amazon CloudFormation/AWS SAM to manage infrastructure Leveraging existing CI/CD tools that have been tweaked to support tools like SAM Difference in telemetry data made up for with more logging and usage of tools like AWS X-Ray Same languages as always: Java, Python, Node.js Little to no changes in development/testing practices: • • • • peer review test in “cloud” linting, syntax checking, unit/service testing canary deploy out slowly & rollback immediately if things go boom © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

Tell me your biggest pain points right now: Limits Scoping the size of a service Proper “stack” boundaries Improving alarms/monitoring Improving testing (always) © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

Tell me your biggest pain points right now: Limits Scoping the size of a service Proper “stack” boundaries AWS Service teams are Improving alarms/monitoring Improving testing (always) © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. just like you!

Tell me your biggest pain points right now: Limits Scoping the size of a service Proper “stack” boundaries AWS Service teams are Improving alarms/monitoring Improving testing (always) just like you! Except……. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

What you can do to be like AWS • Organizational structure aligns with microservice based architecture which aligns well with serverless • Standardized, yet flexible tools made supporting serverless essentially “snapping in” new capabilities • CI/CD is a must • Peer review is the one thing you aren’t doing but should • Understanding when you need a REST API vs. using another invoke model • related: Sync vs. async © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

What you can do to be like AWS • If moving to #serverless feels like a giant shift for your org/team, move slow and purposefully • If someone is telling you that you need all new tools to develop for serverless, they are wrong or selling you something • Potentially something that competes What customers tell me: Serverless benefits pay off vs. the time ramping up © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

?x more Thousands of teams × Microservice architecture If fewer people are needed to × Continuous delivery build things, can we build Multiple environments more× things & faster??? > XXX million deployments a year? © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

About me: Chris Munns - munns@amazon.com, @chrismunns • Principal Developer Advocate - Serverless • New Yorker • Previously: • AWS Business Development Manager – DevOps, July ’15 - Feb ‘17 • AWS Solutions Architect Nov, 2011- Dec 2014 • Formerly on operations teams @Etsy and @Meetup • Little time at a hedge fund, Xerox and a few other startups • Rochester Institute of Technology: Applied Networking and Systems Administration ’05 • Internet infrastructure geek © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

How AWS builds Serverless services using Serverless

Slide 1

Slide 2

Slide 3

Slide 4

Slide 5

Slide 6

Slide 7

Slide 8

Slide 9

Slide 10

Slide 11

Slide 12

Slide 13

Slide 14

Slide 15

Slide 16

Slide 17

Slide 18

Slide 19

Slide 20

Slide 21

Slide 22

Slide 23

Slide 24

Slide 25

Slide 26

Slide 27

Slide 28

Slide 29

Slide 30

Slide 31

Slide 32

Slide 33

Slide 34

Slide 35

Slide 36

Slide 37

Slide 38

Slide 39

Slide 40

Slide 41

Slide 42

Slide 43

Slide 44

Slide 45

Slide 46

Slide 47

Slide 48

Slide 49

Slide 50

Slide 51

Slide 52

Slide 53

Slide 54

Slide 55

Slide 56

Slide 57

Slide 58

Slide 59

Slide 60

Slide 61

Slide 62

Slide 63

Slide 64

Slide 65

Slide 66

Slide 67

Slide 68

Slide 69

Slide 70

Slide 71

Slide 72