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!
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
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”
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
107.
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
118. use our private cloud instead,
it’s totally not a lock-in because containers!
119.
120.
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
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…
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.