Journey to the cloud, the why and how of serverless
•
0 likes•332 views
In this talk, we will look at the evolution from on-premise to the cloud with VMs and containers, and then to serverless.
Report
Share
Journey to the cloud, the why and how of serverless
- 1. Yan Cui @theburningmonk ourneJ Yto the cloud the how and why of serverless
- 6. 2006
- 7. big meetings to decide how to provision new servers
- 8. 3-6 months (!!!!) turn around time
- 9. client tier logic tier data tier SQL
- 11. requires downtime for deployment
- 12. requires downtime for deployment (OK for businesses that aren’t 24/7)
- 13. install monitoring agents/daemons on server
- 16. 2010
- 17. on premise cloud
- 18. 2012
- 19. 2016
- 20. 2019
- 21. EC2 EC2
- 24. EC2 EC2 minutes compute becoming a commodity Genesis Custom-built Product Commodity http://bit.ly/wardley-maps
- 25. EC2 EC2 minutes
- 28. users are distributed around the world systems have to be available 24/7
- 30. SCALABILITY
- 35. Capex Opex capital expenditure operational expenditure
- 36. Capex Opex capital expenditure operational expenditure levelled the playing field
- 37. competition
- 38. competition user demand & expectations
- 40. faster delivery faster feedback loop we need…
- 42. big-bang releases small, frequent releases
- 45. scale
- 46. scale complexity
- 47. but our cognitive capacity hasn’t increased…
- 48. leverage: do more with less
- 49. EC2 EC2
- 51. https://bit.ly/2Im61VK “Unless you’re an infrastructure company, infrastructure is basically overhead.” Matt Klein
- 56. EC2 EC2 EC2 DynamoDB EC2 RDS EC2 SQS DynamoDB
- 57. EC2 EC2 EC2 DynamoDB EC2 RDS EC2 SQS DynamoDB we’re managing lots more infrastructure!
- 58. we need a better abstraction for the “server”
- 59. we need an immutable infrastructure
- 60. 70% utilization monolith 10% utilization x 10 microservices
- 61. 70% utilization monolith 10% utilization x 10 microservices
- 63. EC2 EC2 EC2 DynamoDB EC2 RDS EC2 SQS DynamoDB
- 64. EC2 DynamoDB EC2 RDS EC2 SQS DynamoDB DynamoDB RDS SQS DynamoDB
- 65. EC2 DynamoDB EC2 RDS EC2 SQS DynamoDB DynamoDB RDS SQS DynamoDB
- 66. EC2 docker us-east-1a us-east-1b us-east-1a us-east-1b
- 67. 0 Theory “it works on my machine!” “production ready!”days
- 68. 0 Theory “it works on my machine!” “production ready!”days no log collection
- 69. 0 Theory “it works on my machine!” “production ready!”days no log collection no monitoring no alerting
- 70. 0 Theory “it works on my machine!” “production ready!”days no log collection no monitoring no alerting can’t scale no load balancing
- 71. 0 Theory “it works on my machine!” “production ready!”days no log collection no monitoring no alerting can’t scale no redundancy no load balancing
- 72. 0 Theory “it works on my machine!” “production ready!”days no log collection no monitoring no alerting can’t scale no redundancy what security? no load balancing
- 76. 0 Theory “it works on my machine!” “production ready!” 0 Reality “it works on my machine!” “production ready!” days days
- 78. mooooo..
- 79. 2015
- 80. SQL NoSQL OOP Functional On Premise Cloud Waterfall Agile Monoliths Microservices
- 81. 2016
- 82. 2016
- 86. What do you mean by ‘serverless’?
- 87. “Serverless”
- 89. Gojko Adzic It is serverless the same way WiFi is wireless. http://bit.ly/2yQgwwb
- 90. 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
- 91. “Function-as-a-Service” AWS Lambda Azure Functions Google Cloud Functions Auth0 Webtask Spotinst Functions Kubeless IBM Cloud Functions
- 92. AWS Lambda
- 93. AWS Lambda API Gateway IOT SNS Kinesis CloudWatch
- 97. Simon Wardley Serverless will fundamentally change how we build business around technology and how you code.
- 98. Why serverless?
- 99. more Scalable
- 100. 1,000 concurrent executions (soft limit) 500 increase per minute (hard-ish limit)
- 101. 1,000 concurrent executions (soft limit) 500 increase per minute (hard-ish limit) AUTO-APPROVED RAISE TO 3000
- 102. 1,000 concurrent executions (soft limit) 500 increase per minute (hard-ish limit)
- 106. Resilience (built-in redundancy and multi-AZ)
- 108. Secure
- 111. protection from OS attacks Amazon automatically apply latest patches to host VMs
- 114. Cheaper (don’t pay for idle servers)
- 116. what businesses care about what we can easily measure what most of your budget is spent on
- 117. Deploy
- 127. the DevOps forcethe DevOps force is strong with serverlessis strong with serverless
- 128. 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
- 129. 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
- 130. idea production greater Velocity from idea to product
- 132. less ops responsibility on your shoulders
- 133. infrastructure you
- 134. DynamoDBDynamoDB RDS SQS DynamoDB DynamoDB API Gateway Lambda API Gateway Lambda RDS Lambda DynamoDBSQS
- 135. abstractionlayer
- 137. paradigm shift
- 141. speed
- 147. best practices are still emerging
- 148. ๏ tips for writing Lambda functions ๏ migration to serverless ๏ serverless ops ๏ design patterns ๏ performance optimization ๏ chaos engineering ๏ security ๏ general thoughts and techniques http://bit.ly/theburningmonk-serverless
- 153. there are no silver bullets
- 155. 0 Containers “it works on my machine!” “production ready!”days Serverless 0 “it works!” “production ready!” days
- 156. 0 Containers “it works on my machine!” “production ready!”days Serverless 0 “it works!” “production ready!” days v2! v3! v4! v5! v6!
- 157. EC2 docker us-east-1a us-east-1b us-east-1a us-east-1b Theory
- 158. Reality
- 159. Reality
- 160. scale-to-zero
- 161. serverful serverless us-east-1a us-east-1b us-east-1a us-east-1bscaled to zero!
- 167. serverless is NOT the goal!
- 168. build products customers love to use
- 169. test ideas against the market quickly
- 170. iterate on s
- 172. own less technology, focus on creating Business Values
- 173. own less technology, focus on creating Business Values (serverless is just a good fit for this mindset)
- 174. scaling limits VPC long-running cold starts performance
- 175. scaling limits VPC long-running cold starts performance
- 176. scaling limits VPC long-running cold starts performance
- 180. scaling limits VPC long-running cold starts performance
- 181. FREQUENCY DURATION
- 182. FREQUENCY DURATION dictated by user traffic, out of your control
- 184. minimise the duration of cold starts so they fall within acceptable latency range
- 185. use Node.js, Python or Golang
- 186. trim dependencies
- 193. scaling limits VPC long-running cold starts performance
- 195. scaling limits VPC long-running cold starts performance
- 197. + pay-per-use?
- 198. Simon Wardley Serverless will fundamentally change how we build business around technology and how you code.