Upgrade to Pro — share decks privately, control downloads, hide ads and more …

[DevOps Floripa] Serverless & DevOps

[DevOps Floripa] Serverless & DevOps

Serverless is an architectural style where we don't have servers*, dealing just with third party services. This means almost infinity scaling, less downtime and less maintenance. Of course Serverless isn't a silver bullet, but it can be a good choice.

In this talk, I'll demystify the Serverless concept, introducing its principal provides, architectures, pros and cons – and how the DevOps' culture fits into this new paradigm.

* Kidding: Serverless still has servers ;)


Jonatas Baldin

September 20, 2017


  1. Serverless & DevOps @jonatasbaldin

  2. What is DevOps?

  3. It's an agile collaboration between Devs & Operations

  4. The goal is to eliminate siles, improve feedback across teams,

    reduce risks and deliver value more quickly
  5. The Ops role in the DevOps culture

  6. What is Serverless?

  7. None
  8. FaaS execute code BaaS third-party services

  9. Principles of Serverless

  10. Single Purpose Functions

  11. None
  12. None
  13. Event Driven Architecture

  14. None
  15. Infinity Scalability

  16. None
  17. Pay by Execution

  18. * First 1 million requests per month are free *

    $0.20 per 1 million requests thereafter ($0.0000002 per request)
  19. None
  20. Lots of Third-Party Services

  21. Commercial Providers

  22. Open source Providers

  23. Use Cases Mobile Backends Bots Data Processing IoT

  24. Benefits Infinite Scale Package and Deploy Time to Market Operational

  25. Drawbacks Vendor control/lock-in* No server optimizations No in-server state

  26. Drawbacks Vendor control/lock-in* No server optimizations No in-server state

  27. *Serverless Event Gateway

  28. Opportunities Tooling Open source projects Learning and teaching Improvements

  29. Frameworks

  30. Conferences

  31. None
  32. The Ops role in the Serverless Era

  33. Well...

  34. #NoOps

  35. Just… don't...

  36. None
  37. Serverless doesn't remove Ops complexity, it increases it exponentially

  38. The future of IT Operations and Application Development is less

    about servers and more about services EPX Labs
  39. We now have services for everything!

  40. The Ops efforts should be aimed more towards architecturing these

  41. All services have some kind of limit, and they aren't

    always clear on the documentation
  42. Services providers should be an extension of your engineering team

  43. You should contract services like contracting a fellow coworker

  44. If DevOps is the collaboration between Devs & Operations

  45. Serverless is the collaboration between Devs, Ops and Third Parties

  46. #ServerlessWeekly eepurl.com/cUU8sD

  47. Serverless & DevOps @jonatasbaldin