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 gives you wings

1,454 views

Published on

In this session, we'll talk about why Frontend Developers should care about serverless and how it gives frontend-focused teams the superpower to build scalable backend for their applications without all the traditional overhead of managing the infrastructure themselves.

Published in: Technology
  • Be the first to comment

Serverless gives you wings

  1. 1. Yan Cui @theburningmonk serverless gives you wings
  2. 2. @theburningmonk theburningmonk.com
  3. 3. @theburningmonk theburningmonk.com hey guys, vote on this post and I’ll announce a winner at 10PM tonight
  4. 4. @theburningmonk theburningmonk.com 10PM traffic
  5. 5. @theburningmonk theburningmonk.com 10PM traffic 70-100x
  6. 6. @theburningmonk theburningmonk.com system couldn’t fast enough
  7. 7. @theburningmonk theburningmonk.com updates required 30 mins downtime
  8. 8. @theburningmonk theburningmonk.com features took months to deliver
  9. 9. @theburningmonk theburningmonk.com Dan North “lead time to someone saying thank you is the only reputation metric that matters.”
  10. 10. @theburningmonk theburningmonk.com 6 months, 6 devs
  11. 11. @theburningmonk theburningmonk.com 95% cost saving compared to existing EC2-based solution
  12. 12. @theburningmonk theburningmonk.com velocity went from months to days
  13. 13. Yan Cui http://theburningmonk.com @theburningmonk AWS user for 10 years
  14. 14. @theburningmonk theburningmonk.com 2010
  15. 15. @theburningmonk theburningmonk.com
  16. 16. @theburningmonk theburningmonk.com
  17. 17. @theburningmonk theburningmonk.com users are distributed around the world systems have to be available 24/7
  18. 18. @theburningmonk theburningmonk.com millions of unique daily-active users
  19. 19. SCALABILITY
  20. 20. SCALABILITY RESILIENCE
  21. 21. SCALABILITY RESILIENCE SECURITY
  22. 22. SCALABILITY RESILIENCE SECURITY SPEED
  23. 23. @theburningmonk theburningmonk.com
  24. 24. @theburningmonk theburningmonk.com networking set up VPC set up public subnet set up private subnet set up Internet Gateway set up NAT Gateway configure Route Tables configure Network ACL configure Security Groups
  25. 25. @theburningmonk theburningmonk.com networking VMs apply patches install dependencies create base AMI set up auto-scaling set up multi-AZ set up load balancer configure IAM roles set up logging agent set up VPC set up public subnet set up private subnet set up Internet Gateway set up NAT Gateway configure Route Tables configure Network ACL configure Security Groups
  26. 26. @theburningmonk theburningmonk.com networking VMs apply patches install dependencies create base AMI set up auto-scaling set up multi-AZ set up load balancer configure IAM roles set up logging agent application set up web server configure middlewares set up VPC set up public subnet set up private subnet set up Internet Gateway set up NAT Gateway configure Route Tables configure Network ACL configure Security Groups
  27. 27. @theburningmonk theburningmonk.com networking VMs apply patches install dependencies create base AMI set up auto-scaling set up multi-AZ set up load balancer configure IAM roles set up logging agent application set up web server configure middlewares write 1st line of business logic set up VPC set up public subnet set up private subnet set up Internet Gateway set up NAT Gateway configure Route Tables configure Network ACL configure Security Groups
  28. 28. @theburningmonk theburningmonk.com networking VMs apply patches install dependencies create base AMI set up auto-scaling set up multi-AZ set up load balancer configure IAM roles set up logging agent application set up web server configure middlewares write 1st line of business logic set up VPC set up public subnet set up private subnet set up Internet Gateway set up NAT Gateway configure Route Tables configure Network ACL configure Security Groups
  29. 29. @theburningmonk theburningmonk.com networking VMs apply patches install dependencies create base AMI set up auto-scaling set up load balancer configure IAM roles set up logging agent application set up web server configure middlewares write 1st line of business logic set up VPC set up public subnet set up private subnet set up Internet Gateway set up NAT Gateway configure Route Tables configure Network ACL configure Security Groups mooooo..
  30. 30. @theburningmonk theburningmonk.com but, nonetheless… they’re important for setting you up to succeed
  31. 31. @theburningmonk theburningmonk.com spinning up a web-server a production-ready environment!===
  32. 32. @theburningmonk theburningmonk.com “we ain’t gonna need it”
  33. 33. @theburningmonk theburningmonk.com “we ain’t gonna need it” translation: “we will never be successful”
  34. 34. @theburningmonk theburningmonk.com traffic holy crap, we’ve got traction!
  35. 35. @theburningmonk theburningmonk.com traffic oh no… our server died!
  36. 36. @theburningmonk theburningmonk.com prepare for success
  37. 37. @theburningmonk theburningmonk.com isn’t the savior?
  38. 38. @theburningmonk theburningmonk.com 0 Theory “it works on my machine!” “production ready!”days
  39. 39. @theburningmonk theburningmonk.com
  40. 40. @theburningmonk theburningmonk.com
  41. 41. @theburningmonk theburningmonk.com
  42. 42. @theburningmonk theburningmonk.com 0 Theory “it works on my machine!” “production ready!” 0 Reality “it works on my machine!” “production ready!” days days
  43. 43. @theburningmonk theburningmonk.com
  44. 44. @theburningmonk theburningmonk.com mooooo..
  45. 45. @theburningmonk theburningmonk.com scale
  46. 46. @theburningmonk theburningmonk.com scale complexity
  47. 47. @theburningmonk theburningmonk.com but our cognitive capacity hasn’t increased…
  48. 48. @theburningmonk theburningmonk.com leverage: do more with less
  49. 49. @theburningmonk theburningmonk.com EC2 EC2
  50. 50. @theburningmonk theburningmonk.com EC2 EC2 we’re still managing infrastructure
  51. 51. @theburningmonk theburningmonk.com https://bit.ly/2Im61VK “Unless you’re an infrastructure company, infrastructure is basically overhead.” Matt Klein
  52. 52. @theburningmonk theburningmonk.com infrastructure you
  53. 53. @theburningmonk theburningmonk.com Serverless means… don’t pay for it if no-one uses it don’t need to worry about scaling don’t need to provision and manage servers
  54. 54. @theburningmonk theburningmonk.com “Serverless”
  55. 55. @theburningmonk theburningmonk.com
  56. 56. @theburningmonk theburningmonk.com Gojko Adzic It is serverless the same way WiFi is wireless. http://bit.ly/2yQgwwb
  57. 57. @theburningmonk theburningmonk.com “Function-as-a-Service” AWS Lambda Azure Functions Google Cloud Functions Auth0 Webtask Spotinst Functions Kubeless IBM Cloud Functions
  58. 58. AWS Lambda
  59. 59. AWS Lambda API Gateway IOT SNS Kinesis CloudWatch
  60. 60. @theburningmonk theburningmonk.com Why serverless?
  61. 61. @theburningmonk theburningmonk.com more Scalable
  62. 62. @theburningmonk theburningmonk.com 1,000 concurrent executions (soft limit)
  63. 63. @theburningmonk theburningmonk.com 1,000 concurrent executions (soft limit) AUTO-APPROVED RAISE TO 3000
  64. 64. @theburningmonk theburningmonk.com containers are reused
  65. 65. @theburningmonk theburningmonk.com 100% SERVERLESS IN PRODUCTION
  66. 66. @theburningmonk theburningmonk.com
  67. 67. @theburningmonk theburningmonk.com 80 MILLION MONTHLY USERS
  68. 68. @theburningmonk theburningmonk.com
  69. 69. @theburningmonk theburningmonk.com Cheaper (don’t pay for idle servers)
  70. 70. @theburningmonk theburningmonk.com Resilience (built-in redundancy and multi-AZ)
  71. 71. @theburningmonk theburningmonk.com Secure
  72. 72. @theburningmonk theburningmonk.com idea production greater Velocity from idea to product
  73. 73. @theburningmonk theburningmonk.com idea production choose language + framework master language + framework figure out deployment configure AMI configure ELB configure autoscaling capacity planning over-provision for launch are we doing microservices? configure CI/CD
  74. 74. @theburningmonk theburningmonk.com idea production choose language + framework master language + framework figure out deployment configure AMI configure ELB configure autoscaling capacity planning over-provision for launch are we doing microservices? configure CI/CD
  75. 75. @theburningmonk theburningmonk.com truly “fullstack” developers are rare, and expensive
  76. 76. @theburningmonk theburningmonk.com AWS Scalability Resilience Security DevOps Distributed Systems JavaScript CSS HTML SPA Framework Responsive Design Debugging
  77. 77. @theburningmonk theburningmonk.com AWS Scalability Resilience Security DevOps Distributed Systems JavaScript CSS HTML SPA Framework Responsive Design Debugging
  78. 78. @theburningmonk theburningmonk.com AWS Scalability Resilience Security DevOps Distributed Systems JavaScript CSS HTML SPA Framework Responsive Design Debugging
  79. 79. @theburningmonk theburningmonk.com AWS Scalability Resilience Security DevOps Distributed Systems JavaScript CSS HTML SPA Framework Responsive Design Debugging
  80. 80. @theburningmonk theburningmonk.com what you need to know to build a production-ready backend on AWS EC2 / Containers Serverless
  81. 81. @theburningmonk theburningmonk.com frontend focused teams can delay the point when they need a backend specialist
  82. 82. @theburningmonk theburningmonk.com backend engineers can get so much more done with less effort and stress
  83. 83. @theburningmonk theburningmonk.com what you need to know to build a production-ready backend on AWS EC2 / Containers Serverless AWS basics, DynamoDB, Lambda, SNS, etc.
  84. 84. @theburningmonk theburningmonk.com AppSync DynamoDB Lambda ElasticSearch
  85. 85. @theburningmonk theburningmonk.com focus your time and energy on improving the UX
  86. 86. @theburningmonk theburningmonk.com the backend should “just work”
  87. 87. @theburningmonk theburningmonk.com the backend should “just work” it shouldn’t be THAT hard, and it doesn’t have to
  88. 88. theburningmonk.com/hire-me AdviseTraining Delivery “Fundamentally, Yan has improved our team by increasing our ability to derive value from AWS and Lambda in particular.” Nick Blair Tech Lead
  89. 89. theburningmonk.com/workshops Amsterdam, March 19-20 Helsinki, May 4-5 Stockholm, May 14-15 Dublin, June 16-17 London, September 24-25 Berlin, October 8-9
  90. 90. Production-Ready Serverless
  91. 91. serverlessworkshop.nl 20% off with frontend-love
  92. 92. @theburningmonk theburningmonk.com github.com/theburningmonk

×