You wouldn't build a toast, would you?
•
4 gefällt mir•1,159 views
In 2011, Thomas Thwaites spent 9 months and £1187.54 and built his own toaster. In his own words, he described the toaster as a partial success because "for about five seconds, the toaster toasted, but then unfortunately, the elements kind of melted itself". He is right in the sense that his audacious attempt won him fame and attention, and his TED talk was viewed more than 1M times. But judging his creation on its own and it's an abject failure that was 300 time more expensive than a commercial toaster, took too long to build and was utterly unfit for purpose. As a business that is competing in an increasingly competitive world enabled by advancements in technology, the questions we should be asking ourselves are: "what are the business value, cost and risk in building our own infrastructure vs using a managed service?". In this talk, let's take an objective look at the ongoing debate of containers vs serverless and look at the arguments of control vs responsibility, vendor lock-in and more!
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie You wouldn't build a toast, would you?
Ähnlich wie You wouldn't build a toast, would you? (20)
Mehr von Yan Cui
Mehr von Yan Cui (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
You wouldn't build a toast, would you?
- 1. You wouldn't build your own toaster would you? Yan Cui @theburningmonk
- 10. “ for about five seconds, the toaster toasted, but then unfortunately, the element kind of melted itself ”
- 11. £3.94 9 months + £1187.54
- 16. £3.94 9 months + £1187.54
- 17. £3.94 9 months + £1187.54 OVER BUDGET
- 18. £3.94 9 months + £1187.54 OVER BUDGET OVER TIME
- 19. £3.94 9 months + £1187.54 OVER BUDGET OVER TIME UNUSABLE
- 20. if you depend on a working toaster to survive, what would you do?
- 21. £3.94 A. buy one
- 22. £3.94 9 months + £1187.54 A. buy one B. build your own
- 23. X is a multi-national conglomerate
- 25. 18 months team of 8 2 versions compute platform on
- 26. no documentation
- 30. why???
- 31. Y is a small startup
- 32. We sell socks, but we’re also building our own Kubernetes cluster! Cool, right?
- 34. “in startups, and perhaps in life in general, time is the most scarce resource.” - Yevgeniy Brikman, co-founder of Gruntwork http://bit.ly/2OyvxLq
- 35. if your business depend on the ability to execute code to meet customer needs, what would you do?
- 42. available in Austria, Switzerland, Germany, Japan, Canada, Italy and US
- 43. available on 30+ platforms
- 45. follow @dazneng for updates about the engineering team We’re hiring! Visit engineering.dazn.com to learn more.
- 46. follow @dazneng for updates about the engineering team We’re hiring! Visit engineering.dazn.com to learn more. WE’RE HIRING!
- 47. AWS user since 2009
- 48. AWS user since 2009
- 50. What do you mean by ‘serverless’?
- 51. “Serverless”
- 53. Gojko Adzic It is serverless the same way WiFi is wireless. http://bit.ly/2yQgwwb
- 54. 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
- 55. “Function-as-a-Service” AWS Lambda Azure Functions Google Cloud Functions Auth0 Webtask Spotinst Functions Kubeless IBM Cloud Functions
- 56. AWS Lambda
- 57. AWS Lambda API Gateway IOT SNS Kinesis CloudWatch
- 61. Simon Wardley Serverless will fundamentally change how we build business around technology and how you code.
- 62. Why serverless?
- 63. more Scalable (and scales faster!)
- 64. Cheaper (don’t pay for idle servers)
- 65. Resilience (built-in redundancy and multi-AZ)
- 66. Secure
- 67. 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
- 68. 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
- 69. idea production greater Velocity from idea to product
- 71. less ops responsibility on your shoulders
- 72. idea production greater Velocity from idea to product
- 78. serverless is NOT the goal!
- 79. build products customers love to use
- 80. test ideas against the market quickly
- 81. iterate on s
- 83. own less technology, focus on creating Business Values
- 84. own less technology, focus on creating Business Values (serverless is just a good fit for this mindset)
- 85. serverless technologies are still maturing
- 90. “you have no control over infrastructure” “good luck when Amazon decides to raise the price of Lambda!” “Lambda can’t scale” “you will be locked into AWS”
- 91. “you have no control over infrastructure” “good luck when Amazon decides to raise the price of Lambda!” “Lambda can’t scale” “you will be locked into AWS”
- 92. AWS announced 67 price reductions in the last 5 years, and 0 price hikes
- 93. “you have no control over infrastructure” “good luck when Amazon decides to raise the price of Lambda!” “Lambda can’t scale” “you will be locked into AWS”
- 94. “you have no control over infrastructure” “good luck when Amazon decides to raise the price of Lambda!” “Lambda can’t scale” “you will be locked into AWS”
- 95. 1,000 concurrent executions (soft limit) 500 increase per minute (hard-ish limit)
- 96. 1,000 concurrent executions (soft limit) 500 increase per minute (hard-ish limit) AUTO-APPROVED RAISE TO 3000
- 97. 1,000 concurrent executions (soft limit) 500 increase per minute (hard-ish limit)
- 104. Controlling your own infrastructure comes with Responsibilities
- 105. to take on these responsibilities you need to have the relevant skills sets in the organization Controlling your own infrastructure comes with Responsibilities
- 106. to take on these responsibilities you need to have the relevant skills sets in the organization Controlling your own infrastructure comes with Responsibilities ENGINEERS
- 108. to take on these responsibilities you need to have the relevant skills sets in the organization Controlling your own infrastructure comes with Responsibilities ENGINEERS ADMIN
- 109. to take on these responsibilities you need to have the relevant skills sets in the organization Controlling your own infrastructure comes with Responsibilities ENGINEERS ADMIN RECRUITMENT
- 110. to take on these responsibilities you need to have the relevant skills sets in the organization Controlling your own infrastructure comes with Responsibilities ENGINEERS ADMIN RECRUITMENT MARKET
- 112. what are you paying for?
- 113. guard against the temptation to look for control for control sake
- 114. AWS Lambda, Azure Functions, Google Cloud Functions Your custom, container-based, general purpose compute platform
- 116. Lock-in risk Reward
- 117. “VENDOR LOCK-IN IS THE ROOT OF ALL EVIL”
- 118. use our private cloud instead, it’s totally not a lock-in because containers!
- 121. to take on these responsibilities you need to have the relevant skills sets in the organization Controlling your own infrastructure comes with Responsibilities ENGINEERS ADMIN RECRUITMENT MARKET
- 122. risk is just one side of the coin
- 124. extracting maximum value from your cloud provider minimising undifferentiated heavy-lifting faster time-to-market reward
- 125. vendor lock-in is a problem that is all bark but no bite
- 127. own less technology, focus on creating Business Values
- 129. “DATABASE LOCK-IN IS THE ROOT OF ALL EVIL”
- 130. ORM
- 131. a load of unnecessary complexity that didn’t end up making DB migrations any easier, and forced you to the least common denominator of feature sets and stop you from taking advantage of your DB in the first place…
- 132. nooooooooooo, wish I hadn’t used an ORM!!
- 134. The true danger with 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.
- 135. is vendor lock-in a risk? YES
- 136. is the return worth the risk? ABSOLUTELY!
- 137. there are no silver bullets
- 140. control comes with its own baggages
- 141. but sometimes the benefits outweigh the baggages