Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Serverless and DevOps

648 views

Published on

From July 2015 until January 2017 I represented the DevOps service space at AWS. I traveled the world and spoke about DevOps culture, practices and tools to companies small and large. Then I left for AWS Lambda team and now travel the world helping developers understand this new application paradigm that is serverless. People often ask me, what does serverless mean for DevOps? What does DevOps mean for serverless? In this talk I’ll give the AWS perspective and help clear up the future of both, talk about the culture, practice, and tools of serverless application development and explain what you should do if DevOps is in your title.

Published in: Technology
  • Be the first to comment

Serverless and DevOps

  1. 1. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Chris Munns – Senior Developer Advocate – AWS Serverless Serverless and DevOps
  2. 2. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Chris Munns – Senior Developer Advocate – AWS Serverless Serverless and DevOps?
  3. 3. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. About me: Chris Munns - munns@amazon.com, @chrismunns • Senior 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
  4. 4. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. https://secure.flickr.com/photos/mgifford/4525333972 Why are we here today?
  5. 5. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Hi, my name is Chris Munns and I am a recovering believer that DevOps is the future of IT
  6. 6. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. About me: Chris Munns - munns@amazon.com, @chrismunns • Senior 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
  7. 7. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. At AWS, Product Biz-Dev is glue between orgs Product Teams Product Marketing Teams “the Field”
  8. 8. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. aws.amazon.com/devops
  9. 9. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. aws.amazon.com/devops/partner-solutions/
  10. 10. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. I traveled all over and talked about DevOps <- me
  11. 11. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. What is DevOps?
  12. 12. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. What is DevOps? Cultural Philosophy Practices Tools
  13. 13. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. 5 Key DevOps technology areas: • Continuous Integration/Delivery • Infrastructure as Code • Monitoring/Metrics/Logging/APM • APIs/Microservices Management • Communication & Collaboration
  14. 14. Tearing down the wall between: • Developers and Operations • Devs and Ops and QA • Devs and Ops and QA and Security • etc https://www.flickr.com/photos/brostad/2364099378/ What is DevOps?
  15. 15. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Today I’m going to be referring mostly to the role of “Ops” in DevOps
  16. 16. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. 2 Pizza Teams at Amazon � A “micro-startup” inside of Amazon � ~6-10 people per � Full ownership � Full accountability � Aligned incentives � “DevOps” from a culture/practices/tools perspective � Most teams are just Product Management and Developers
  17. 17. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. 2 Pizza Teams at Amazon Teams are responsible for EVERYTHING about their infrastructure* � No centralized Ops � No Tier 1/2/3 Support � No NOC anywhere � Teams share on-call rotations � No SRE Org � Limited # of “Systems Engineers” that help teams in specialized situations with infrastructure management *sit tight a slide
  18. 18. © 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
  19. 19. © 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 ….
  20. 20. © 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?
  21. 21. © 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
  22. 22. © 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
  23. 23. © 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
  24. 24. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
  25. 25. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. OK. So what does this all mean for DevOps/Ops/SRE folks?
  26. 26. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Managing servers with infrastructure as code: Hi yes, I’d like to run an application on a server please....
  27. 27. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Managing servers with infrastructure as code: Hi yes, I’d like to run an application on a server please....
  28. 28. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Managing servers with infrastructure as code: Hi yes, I’d like to run an application on a server please.... $ find ./ | xargs wc –l ... 47769 total
  29. 29. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Managing servers with infrastructure as code: Hi yes, I’d like to run an application on a server please....
  30. 30. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Meet SAM!
  31. 31. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. From: https://github.com/awslabs/aws-serverless-samfarm/blob/master/api/saml.yaml <-THIS BECOMES THIS-> AWS SAM Templates
  32. 32. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. AWS SAM Globals Globals: Function: Runtime: nodejs4.3 CodeUri: s3://code-artifacts/pet_app1234.zip MemorySize: 1024 Timeout: 30 AutoPublishAlias: !Ref ENVIRONMENT getDogsFunction: Type: AWS::Serverless::Function Properties: Handler: getdogs.handler Events: GetDogs: Type: Api Properties: Path: /Dogs Method: ANY getCatsFunction: Type: AWS::Serverless::Function Properties: Handler: getCats.handler Events: GetCats: Type: Api Properties: Path: /Cats Method: ANY getBirdsFunction: Type: AWS::Serverless::Function Properties: Handler: getBirds.handler Timeout: 15 Events: GetBirds: Type: Api Properties: Path: /Birds Method: ANY
  33. 33. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. AWS SAM Policy Templates MyQueueFunction: Type: AWS::Serverless::Function Properties: ... Policies: # Gives permissions to poll an SQS Queue - SQSPollerPolicy: queueName: !Ref MyQueue ... MyQueue: Type: AWS::SQS::Queue ...
  34. 34. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. From: 12factor.net
  35. 35. The 12 Factors & Serverless Applications: 1. Codebase 2. Dependencies 3. Config 4. Backing services 5. Build, release, run 6. Process 7. Port Binding 8. Concurrency 9. Disposability 10.Dev/prod parity 11.Logs 12.Admin processes = Works similarly = Not relevant Taken from: https://amzn.to/2o7dzzQ
  36. 36. The 12 Factors & Serverless Applications: 1. Codebase 2. Dependencies 3. Config 4. Backing services 5. Build, release, run 6. Process 7. Port Binding 8. Concurrency 9. Disposability 10.Dev/prod parity 11.Logs 12.Admin processes = Works similarly = Not relevant Taken from: https://amzn.to/2o7dzzQ How many of these require Ops?
  37. 37. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. But surely there are other infrastructure things to manage?
  38. 38. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
  39. 39. © 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:
  40. 40. © 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.
  41. 41. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. 5 Key DevOps technology areas: • Continuous Integration/Delivery • Infrastructure as Code • Monitoring/Metrics/Logging/APM • APIs/Microservices Management • Communication & Collaboration
  42. 42. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. 5 Key DevOps technology areas: • Continuous Integration/Delivery • Infrastructure as Code • Monitoring/Metrics/Logging/APM • APIs/Microservices Management • Communication & Collaboration Provided with deep integration by almost all major cloud providers OR ISVs with managed offerings
  43. 43. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. What’s left for DevOps/Ops/SRE in the cloud today? • Networking • Relational Database tuning • Managing self managed databases • Managing the interaction/connection back to “legacy” systems/infrastructure • Typically: control of AWS accounts
  44. 44. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. What’s left for DevOps/Ops/SRE in the cloud today? • Networking • Relational Database tuning • Managing self managed databases • Managing the interaction/connection back to “legacy” systems/infrastructure • Typically: control of AWS accounts But for how long?
  45. 45. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. FIN/ACK Will we need the Ops in DevOps?
  46. 46. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. FIN/ACK Short term == Yes Long term == ??? Will we need the Ops in DevOps?
  47. 47. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. FIN/ACK Short term == Yes Long term == ??? Will we need the Ops in DevOps? And without Ops, is it even DevOps? Or just new modern app development?
  48. 48. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. FIN/ACK What’s an “Ops” to do? • In the future “value add” for business is going to be in developing product • Learn to develop, something, frontend or backend • Groups perceived as “Cost centers” are going to be scrutinized even further as businesses look to control investment in the cloud • Don’t ignore the smoke signals • “NoOps” has been a topic for a few years now • Limits/rough edges in #serverless going away faster and faster • DCO at Amazon is almost always hiring (https://www.amazon.jobs/datacenter)
  49. 49. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Chris Munns munns@amazon.com @chrismunnshttps://www.flickr.com/photos/theredproject/3302110152/
  50. 50. © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. https://secure.flickr.com/photos/dullhunk/202872717/

×