Save 37% off PRO during our Black Friday Sale! »

Serverless DevOps: This is What We Do When The Server Goes Away!

Serverless DevOps: This is What We Do When The Server Goes Away!

What does the role of an ops person look like when building a serverless application? This is the work that fills the day.

24794783b45c456b21ff78d6d8259456?s=128

Tom McLaughlin

July 26, 2019
Tweet

Transcript

  1. @tmclaughbos THIS IS WHAT WE DO WHEN THE SERVER GOES

    AWAY! SERVERLESS DEVOPS
  2. @tmclaughbos BYE SERVERS

  3. @tmclaughbos

  4. @tmclaughbos

  5. @tmclaughbos "IF YOU DON’T CODE THEN YOU’RE JUST AN I.T.

    PERSON” A Former VPoE to me
  6. @tmclaughbos

  7. @tmclaughbos WHAT IS SERVERLESS?

  8. @tmclaughbos WHAT IS SERVERLESS? • No servers to manage or

    provision • Pay only for what you actively use • System components scales with usage • Availability and fault tolerance built in
  9. @tmclaughbos

  10. @tmclaughbos WHAT IS SERVERLESS? • No servers to manage or

    provision • Pay only for what you actively use • System components scales with usage • Availability and fault tolerance built in
  11. @tmclaughbos FUNCTIONS AS A SERVICE (FAAS) Event Function Service •Api

    Request •Message Received •State Change •Python •Go •JavaScript •Java •C# •PowerShell •Datastore •Queue •Message Bus •3rd Party API
  12. @tmclaughbos BEHOLD… SERVERLESS!

  13. @tmclaughbos WHAT DOES SERVERLESS MEAN FOR US?

  14. @tmclaughbos GET RID OF YOUR OPS TEAM

  15. @tmclaughbos YOUR DEVOPS TRANSFORMATION Pre-DevOps DevOps

  16. @tmclaughbos YOUR DEVOPS TRANSFORMATION REALITY

  17. @tmclaughbos VALUE DELIVERY TEAMS

  18. @tmclaughbos VALUE DELIVERY TEAMS

  19. @tmclaughbos DEVOPS PROMISE LAND: FULLY CROSS-FUNCTIONAL TEAMS

  20. @tmclaughbos WELCOME TO THE DELIVERY TEAM… NOW WHAT?

  21. @tmclaughbos APPLICATION DESIGN & ARCHITECTURE

  22. @tmclaughbos

  23. @tmclaughbos

  24. @tmclaughbos

  25. @tmclaughbos DEVELOPMENT

  26. @tmclaughbos DEVELOPER FRICTION

  27. @tmclaughbos NON-PRODUCT FEATURES

  28. @tmclaughbos SUPPORT SYSTEMS

  29. @tmclaughbos

  30. @tmclaughbos OPERATIONS

  31. @tmclaughbos MAKING SYSTEMS BETTER HANDLE FAILURE

  32. @tmclaughbos MAKING SYSTEMS BETTER HANDLE FAILURE

  33. @tmclaughbos FIND DOWNSTREAM / FIX UPSTREAM { "_id": "00535cb6-443d-11e9-982d-8c859074f8c7", "location":

    { "latitude": "", "longitude": "" }, "user": { "firstname": "Tom", "lastname": "McLaughlin" } }
  34. @tmclaughbos CHALLENGES

  35. @tmclaughbos NEED TO CODE

  36. @tmclaughbos DEV TEAM PROCESSES

  37. @tmclaughbos

  38. @tmclaughbos DEVELOPERS DEVELOPERS DEVELOPERS

  39. @tmclaughbos IS YOUR JOB GOING TO CHANGE TOMORROW?

  40. @tmclaughbos PROBABLY NOT

  41. @tmclaughbos

  42. @tmclaughbos

  43. @tmclaughbos https://www.serverlessops.io/ebook

  44. @tmclaughbos