Serverless 5 Takeaways

Serverless 5 Takeaways

First, an introduction to Serverless and then 5 key takeaways

8f43892395260c6ad14618987099ddcc?s=128

Serhat Can

April 13, 2019
Tweet

Transcript

  1. 2.
  2. 4.
  3. 7.
  4. 11.

    @srhtcn Ahmet wrote an amazing “Hello world” application. He thinks

    it is helpful. He wants to put it live: • Rents a server • Install OS, language, configure server • Upload and run the app
  5. 12.

    @srhtcn People start using the app and want more features!

    • Add more servers, avoid downtime • Build and manage VM images • Language, configuration updates • Logs should be stored somewhere • Add some Docker magic • Monitor, Scale, Rollback, optimize costs
  6. 13.

    @srhtcn Ahmet needs a “DevOps engineer” • Code in Python,

    Java, shell • Expert in AWS • CI/CD pipelines, Jenkins • Linux master • Ansible, Chef, Puppet, Git, Bitbucket
  7. 14.

    @srhtcn Ahmet needs a “DevOps engineer” • Code in Python,

    Java, shell • Expert in AWS • CI/CD pipelines, Jenkins • Linux master • Ansible, Chef, Puppet, Git, Bitbucket • Maaş: 5000-6000 TL
  8. 15.

    @srhtcn Ahmet needs a “DevOps engineer” • Code in Python,

    Java, shell • Expert in AWS • CI/CD pipelines, Jenkins • Linux master • Ansible, Chef, Puppet, Git, Bitbucket • Maaş: 5000-6000 TL
  9. 17.
  10. 18.

    @srhtcn Bare metal IaaS (VMs) CaaS (containers) Cloud computing models

    PaaS (Heroku, Elasticbean stalk) FaaS (YAY! Serverless!) AWS Amplify?!
  11. 19.

    @srhtcn Pay per use, really No charge when code is

    not running Create value Focus on what really matters, ship fast
  12. 20.

    @srhtcn Serverless is a cloud model where you • pay

    only for the time your code is executed • focus on providing business value, not managing your cloud environment.
  13. 23.

    @srhtcn Our experience at 2015 Writing custom integrations for our

    customers 2016 AWS Lambda for ops tasks on production 2017 A new customer facing feature on AWS Lambda 2018 A Spin Off: Thundra - Observability for AWS Lambda
  14. 25.
  15. 26.

    @srhtcn • Event driven everything! • Functions should be idempotent

    • Stateless with a twist • Choose additional tools wisely Serverless doesn’t remove the need for great engineers
  16. 29.

    @srhtcn Serverless is LessOps, not NoOps • Build delivery pipeline

    and deployment strategy • Monitoring has to be a first-class citizen • Cold starts • Infinite scale but not really !?
  17. 32.

    @srhtcn Serverless is usually cheaper, event at scale • Free

    tier and 100ms based pricing • Total cost of ownership • No initial investment (just code, less ops) • Less maintenance cost • Engineering workforce cost • You are probably not Spotify or Netflix, even they…
  18. 37.

    @srhtcn Serverless isn’t just for a couple of use-cases •

    FaaS is great for connecting stuff on the cloud • If it is event-driven, it can be done with FaaS / Serverless • There is support for bring your own language • API Gateway has websocket support though! • Commonly used for data and stream processing, ETL jobs, building APIs…
  19. 39.
  20. 40.

    @srhtcn • Of course assess potential risks and impact •

    No big cloud vendor increased its prices, pick one • Building abstractions is time consuming and counter productive • Loss of opportunity costs more Vendor lock-in is often a myth
  21. 41.

    @srhtcn Takeways 1. Still need great engineers. 2. LessOps, not

    NoOps 3. Cheaper, even at scale 4. Can do many use-cases 5. Vendor lock-in myth
  22. 42.

    @srhtcn Serverless computing will become the default computing paradigm of

    the Cloud Era. https://www2.eecs.berkeley.edu/Pubs/TechRpts/2019/EECS-2019-3.pdf