Downloaded 26 times
Uploaded byYan Cui
Debunking serverless myths
The document discusses the concept of serverless computing, debunking common myths such as cold starts, costs, and control issues, while highlighting its advantages including scalability, cost-effectiveness, and reduced operational overhead. It emphasizes that serverless technologies allow developers to focus more on building value rather than managing infrastructure, although vendors may invoke concerns about lock-in risks. Ultimately, it argues that while risks exist, the benefits of adopting serverless architecture often outweigh these challenges, enabling businesses to innovate faster.
More Related Content
Similar to Debunking serverless myths
Debunking serverless myths
- 1. Debunking Serverless Myths Yan Cui@theburningmonk
- 2.
- 3.
- 4.
- 6.
- 7. What do youmean by ‘serverless’?
- 8.
- 10. Gojko Adzic It isserverless the same way WiFi is wireless. http://bit.ly/2yQgwwb
- 11. Serverless means… don’t payfor it if no-one uses it don’t need to worry about scaling don’t need to provision and manage servers
- 12. “Function-as-a-Service” AWS Lambda Azure Functions GoogleCloud Functions Auth0 Webtask Spotinst Functions Kubeless IBM Cloud Functions
- 13.
- 14. AWS Lambda API GatewayIOT SNS Kinesis CloudWatch
- 15.
- 16.
- 17.
- 18. Simon Wardley Serverless willfundamentally change how we build business around technology and how you code.
- 19.
- 20. more Scalable (and scalesfaster!)
- 21. Cheaper (don’t pay foridle servers)
- 22. Resilience (built-in redundancy andmulti-AZ)
- 23.
- 24. 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
- 25. 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
- 26. idea production greater Velocityfrom idea to product
- 27.
- 28. less ops responsibilityon your shoulders
- 30.
- 32.
- 33.
- 34. serverless is NOTthe goal!
- 35. build products customerslove to use
- 36. test ideas againstthe market quickly
- 37.
- 38.
- 39. own less technology, focuson creating Business Values
- 40. own less technology, focuson creating Business Values (serverless is just a good fit for this mindset)
- 41. serverless technologies arestill maturing
- 42.
- 43. DEBUNKING SERVERLESS MYTHS COLDSTARTS COLD STARTS overplays or underplays the role of cold starts on serverless performance MYTH #1
- 44. DEBUNKING SERVERLESS MYTHS COLDSTARTS COLD STARTS overplays or underplays the role of cold starts on serverless performance MYTH #1 COSTSCOSTS misunderstands thereal cost savings fromadopting serverless MYTH #2
- 45. DEBUNKING SERVERLESS MYTHS COLDSTARTS COLD STARTS overplays or underplays the role of cold starts on serverless performance MYTH #1 COSTSCOSTS misunderstands thereal cost savings fromadopting serverless MYTH #2 CONTROL not realise that control of infra requires expensive skillsets to manage MYTH #3 CONTROL
- 46. DEBUNKING SERVERLESS MYTHS COLDSTARTS COLD STARTS overplays or underplays the role of cold starts on serverless performance MYTH #1 COSTSCOSTS misunderstands thereal cost savings fromadopting serverless MYTH #2 CONTROL not realise that control of infra requires expensive skillsets to manage MYTH #3 CONTROL LOCK-INnot realise that lock-in risk rewards productivity, and true lock-in is dataMYTH #4 LOCK-IN
- 47. COLD STARTSCOLD STARTS overplaysor underplays the role of cold starts on serverless performance MYTH #1 LOCK-IN not realise that lock-in risk rewards productivity, and true lock-in is data MYTH #4 LOCK-INCONTROL not realise that control of infra requires expensive skillsets to manage MYTH #3 CONTROLCOSTSCOSTS misunderstands the real cost savings from adopting serverless MYTH #2
- 48.
- 49.
- 50. “cold starts onlyhappen to the first request”
- 51. function invocationconcurrent execution i.e.a container
- 52. function invocationconcurrent execution i.e.a container class instance method call
- 53. Lambda scales thenumber of concurrent executions based on traffic
- 54. existing “containers” arereused where possible
- 55.
- 56.
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 63.
- 64.
- 69.
- 70. FREQUENCY DURATION dictated byuser traffic, out of your control
- 71.
- 72. “Lambda is nota suitable solution for me because of cold starts”
- 73. “what is yourlatency requirement?”
- 74. cold starts thatdon’t add to user-facing latency is generally not worth worrying about
- 75. Node.js functions, noVPC, 1GB, averages ~500ms cold start with production workload
- 76. Node.js functions, noVPC, 1GB, averages ~500ms cold start with production workload (good enough for most web applications)
- 77. sporadic spikes latencyexisted before Lambda
- 78.
- 79.
- 80.
- 81.
- 82. cold starts isgenerally not an issue if you have a steady traffic pattern
- 83.
- 84.
- 85.
- 86. minimise the durationof cold starts so they fall within acceptable latency range
- 87. use higher memorysetting if function performs CPU intensive work
- 88. use Node.js, Pythonor Golang
- 89.
- 90.
- 91. avoid VPCs (fornow) unless you need to access VPC-protected resources
- 92. COSTSCOSTS misunderstands the real costsavings from adopting serverless MYTH #2 LOCK-IN not realise that lock-in risk rewards productivity, and true lock-in is data MYTH #4 LOCK-INCONTROL not realise that control of infra requires expensive skillsets to manage MYTH #3 CONTROL
- 93. “good luck whenAmazon decides to raise the price of Lambda!”
- 94. mind the marketforce…
- 95. AWS announced 67price reductions in the last 5 years, and 0 price hikes
- 97. Model Training Low-latency Prediction Servingvia Batching
- 99.
- 103. the platforms needto do better at educating users on how to choose between different services
- 104.
- 105. https://www.doc.ic.ac.uk/~rbc/papers/fse-serverless-17.pdf “This paper presentstwo case industrial studies of early adopters, showing how migrating an application to the Lambda deployment architecture reduced hosting costs – by between 66% and 95%…”
- 106. what we caneasily measure
- 108. what most ofyour budget is spent on
- 109. what businesses care about whatwe can easily measure what most of your budget is spent on
- 110. leverage: do morewith less
- 111. 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
- 112.
- 113. Serverless might costyou just as much, or even more, but you get so much more done
- 115. 6 developers, 6months 95% saving against EC2 15x no. of production releases per month
- 117. CONTROL not realise thatcontrol of infra requires expensive skillsets to manage MYTH #3 CONTROL LOCK-IN not realise that lock-in risk rewards productivity, and true lock-in is data MYTH #4 LOCK-IN
- 118.
- 122. Controlling your owninfrastructure comes with Responsibilities
- 123. to take onthese responsibilities you need to have the relevant skillsets in the organization Controlling your own infrastructure comes with Responsibilities
- 124. to take onthese responsibilities you need to have the relevant skillsets in the organization Controlling your own infrastructure comes with Responsibilities ENGINEERS
- 126. to take onthese responsibilities you need to have the relevant skillsets in the organization Controlling your own infrastructure comes with Responsibilities ENGINEERS ADMIN
- 127. to take onthese responsibilities you need to have the relevant skillsets in the organization Controlling your own infrastructure comes with Responsibilities ENGINEERS ADMIN RECRUITMENT
- 128. to take onthese responsibilities you need to have the relevant skillsets in the organization Controlling your own infrastructure comes with Responsibilities ENGINEERS ADMIN RECRUITMENT MARKET
- 130. what are youpaying for?
- 131. guard against thetemptation to look for control for control sake
- 132. AWS Lambda, AzureFunctions, Google Cloud Functions Your custom, container-based, general purpose compute platform
- 134. LOCK-IN not realise thatlock-in risk rewards productivity, and true lock-in is data MYTH #4 LOCK-IN
- 135.
- 136. it’s not alock-in, it’s a form of coupling that has a switching cost
- 137.
- 138. “vendor lock-in” switching cost “let’savoid lock-in” prevention cost
- 140. The true dangerwith lock-in, especially with serverless, is the potential for data lock-in. Data has gravity. It accumulates. Data is economically disincentivized to leave, by way of platform pricing. This is the single biggest threat to vendor choice.
- 141. Newton’s 41st law:data has gravity
- 142. Newton’s 42nd law:data migration is gonna suck
- 143.
- 146. “VENDOR LOCK-IN ISTHE ROOT OF ALL EVIL”
- 147. to take onthese responsibilities you need to have the relevant skills sets in the organization Controlling your own infrastructure comes with Responsibilities ENGINEERS ADMIN RECRUITMENT MARKET
- 148. if you alreadyhave the expertise, can their time be better used to generate more business value instead?
- 149. risk is justone side of the coin
- 151. extracting maximum valuefrom your cloud provider minimising undifferentiated heavy-lifting faster time-to-market reward
- 153. own less technology, focuson creating Business Values
- 154. is vendor lock-ina risk? YES
- 155. is the returnworth the risk? ABSOLUTELY!
- 156. there are nosilver bullets
- 158.
- 159. control comes withits own baggages
- 160. but sometimes thebenefits outweigh the baggages
- 163. https://theburningmonk.com/hire-me AdviseTraining Delivery “Fundamentally, Yanhas improved our team by increasing our ability to derive value from AWS and Lambda in particular.” Nick Blair Tech Lead
- 164.