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.
A WIN
FOR
DEVELOPERS
NOT
JUST
BUSINESSES
serverless:
the why of technology is to
solve business problems and
create business values
my job as an engineer is NOT to write code
the code is not the product
the code is not the product
it’s a cost, a means to an end
my job as an engineer is to create value
what is the biggest challenge
facing your company?
finding market fit
runway
runway: f(investment, cost) => time
John Richard Boyd
US air force colonel
“Fighter Pilot who changed the Art of War”
OODA loop
Observe
OODA loop
collect data
Observe Orient
OODA loop
collect data analyse data,
form metal model
Observe Orient Decide
OODA loop
collect data analyse data,
form metal model
decide course
of action
Observe Orient Decide Act
OODA loop
collect data analyse data,
form metal model
decide course
of action
action!
Observe Orient Decide Act
OODA loop
collect data analyse data,
form metal model
decide course
of action
action!
Observe Orient Decide Act
OODA loop
product development
Observe Orient Decide Act
OODA loop
Understand
product development
Observe Orient Decide Act
OODA loop
Understand Define
product development
Observe Orient Decide Act
OODA loop
Understand Define Design
product development
Observe Orient Decide Act
OODA loop
Understand Define Design Deliver
product development
Boyd’s Law of Iteration
Boyd decided that the primary determinant to winning dogfights
was not observing, orienting, planni...
Boyd’s Law of Iteration
Boyd decided that the primary determinant to winning dogfights
was not observing, orienting, planni...
runway
runway
communication overhead
communication overhead
inter-team dependencies
communication overhead
inter-team dependencies
lack of autonomy
Yan Cui
http://theburningmonk.com
@theburningmonk
Independent Consultant
Advisor @
Instructor @
Instructor @
AWS user since 2009
AWS user since 2009
2006
big meetings to decide how to provision new servers
3-6 months (!!!!) turn around time
client tier
logic tier
data tier
SQL
monolithic, 3-tier architectures
requires downtime for deployment
requires downtime for deployment
(OK for businesses that aren’t 24/7)
big-bang releases
2010
on premise cloud
EC2
EC2
EC2
EC2
months minutes
EC2
EC2
months minutes
EC2
EC2
minutes
compute becoming a commodity
Genesis Custom-built Product Commodity
http://bit.ly/wardley-maps
EC2
EC2
minutes
users are distributed
around the world
systems have to be
available 24/7
SCALABILITY
SCALABILITY
RESILIENCE
SCALABILITY
RESILIENCE
SECURITY
SCALABILITY
RESILIENCE
SECURITY
SPEED
Capex Opex
capital expenditure operational expenditure
Capex Opex
capital expenditure operational expenditure
levelled the playing field
competition
competition user demand &
expectations
faster delivery
faster feedback loop
we need…
big-bang releases small, frequent releases
co-evolution
waterfall agile
silos DevOps
practice
activity
of
and
scale
scale complexity
but our cognitive capacity hasn’t increased…
leverage: do more with less
EC2
EC2
EC2
EC2
we’re still managing
infrastructure
https://bit.ly/2Im61VK
“Unless you’re an infrastructure company,
infrastructure is basically overhead.”
Matt Klein
infrastructure
you
EC2EC2
EC2 RDSDynamoDB SQS
Monoliths Microservices
EC2
EC2
EC2 DynamoDB
EC2 RDS
EC2 SQS DynamoDB
EC2
EC2
EC2 DynamoDB
EC2 RDS
EC2 SQS DynamoDB
we’re managing
lots more
infrastructure!
we need a better abstraction for the “server”
we need an immutable infrastructure
70% utilization
monolith
10% utilization
x 10
microservices
70% utilization
monolith
10% utilization
x 10
microservices
0
Theory
“it works on
my machine!”
“production
ready!”days
0
Theory
“it works on
my machine!”
“production
ready!”
0
Reality
“it works on
my machine!”
“production
ready!”
days
days
mooooo..
runway
runway
how do we optimize the runway
to get more iterations out of it?
runway
we need cheaper and
lighter planes!
2016
2016
Server-ful Serverless
2016
95% cost saving vs EC2
2016
95% cost saving vs EC2
15x number of production deploys
2016
95% cost saving vs EC2
15x number of production deploys
same sized team
minimise undifferentiated
heavy-lifting
Why serverless?
more Scalable
Cheaper
(don’t pay for idle servers)
2016
95% cost saving vs EC2
https://aws.amazon.com/solutions/case-studies/financial-engines/
https://www.doc.ic.ac.uk/~rbc/papers/fse-serverless-17.pdf
“This paper presents two
case industrial studies of
early adopt...
Resilience
(built-in redundancy and multi-AZ)
http://bit.ly/2Vzfexo
Secure
Shared Responsibility Model
protection from OS attacks
Amazon automatically apply latest patches to host VMs
request
blue-green deployment
req/s
auto-scaling
us-east-1a
us-east-1b
us-east-1c
multi-AZ
the DevOps forcethe DevOps force
is strong with serverlessis strong with serverless
idea production
choose language
+ framework
master language
+ framework
figure out
deployment
configure AMI
configure ELB
con...
idea production
choose language
+ framework
master language
+ framework
figure out
deployment
configure AMI
configure ELB
con...
idea production
choose language
+ framework
master language
+ framework
figure out
deployment
configure AMI
configure ELB
con...
idea production
greater Velocity from idea to product
2016
15x number of production deploys
same sized team
leverage: do more with less
focus on customer needs
https://bit.ly/2Im61VK
“Unless you’re an infrastructure company,
infrastructure is basically overhead.”
Matt Klein
building a resilient, and scalable
infrastructure is hard work
building a resilient, and scalable
infrastructure is hard work
and crucial to
your success!
diverts attention from core
business problems
creates inter-team dependency
leading to delays, and time
pressure and stress
serverless teams are smaller,
and happier!
smaller teams
less comm overhead
fewer meetings
more time getting stuff done!
developers are able to own more of
their stack
developers are able to own more of
their stack
more autonomy
leverage: do more with less
cheaper, lighter, go faster
competition waits for no one
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Serverless is a win for businesses, not just developers
Upcoming SlideShare
Loading in …5
×

Serverless is a win for businesses, not just developers

In this talk, we discussed why businesses should care about serverless and why it's not just a tool for developers.

  • Be the first to comment

Serverless is a win for businesses, not just developers

  1. 1. A WIN FOR DEVELOPERS NOT JUST BUSINESSES serverless:
  2. 2. the why of technology is to solve business problems and create business values
  3. 3. my job as an engineer is NOT to write code
  4. 4. the code is not the product
  5. 5. the code is not the product it’s a cost, a means to an end
  6. 6. my job as an engineer is to create value
  7. 7. what is the biggest challenge facing your company?
  8. 8. finding market fit
  9. 9. runway
  10. 10. runway: f(investment, cost) => time
  11. 11. John Richard Boyd US air force colonel “Fighter Pilot who changed the Art of War”
  12. 12. OODA loop
  13. 13. Observe OODA loop collect data
  14. 14. Observe Orient OODA loop collect data analyse data, form metal model
  15. 15. Observe Orient Decide OODA loop collect data analyse data, form metal model decide course of action
  16. 16. Observe Orient Decide Act OODA loop collect data analyse data, form metal model decide course of action action!
  17. 17. Observe Orient Decide Act OODA loop collect data analyse data, form metal model decide course of action action!
  18. 18. Observe Orient Decide Act OODA loop product development
  19. 19. Observe Orient Decide Act OODA loop Understand product development
  20. 20. Observe Orient Decide Act OODA loop Understand Define product development
  21. 21. Observe Orient Decide Act OODA loop Understand Define Design product development
  22. 22. Observe Orient Decide Act OODA loop Understand Define Design Deliver product development
  23. 23. Boyd’s Law of Iteration Boyd decided that the primary determinant to winning dogfights was not observing, orienting, planning, or acting better. The primary determinant to winning dogfights was observing, orienting, planning, and acting faster. In other words, how quickly one could iterate. Speed of iteration, Boyd suggested, beats quality of iteration.
  24. 24. Boyd’s Law of Iteration Boyd decided that the primary determinant to winning dogfights was not observing, orienting, planning, or acting better. The primary determinant to winning dogfights was observing, orienting, planning, and acting faster. In other words, how quickly one could iterate. Speed of iteration, Boyd suggested, beats quality of iteration.Speed of iteration, Boyd suggested, beats quality of iteration.
  25. 25. runway
  26. 26. runway
  27. 27. communication overhead
  28. 28. communication overhead inter-team dependencies
  29. 29. communication overhead inter-team dependencies lack of autonomy
  30. 30. Yan Cui http://theburningmonk.com @theburningmonk Independent Consultant Advisor @ Instructor @ Instructor @
  31. 31. AWS user since 2009
  32. 32. AWS user since 2009
  33. 33. 2006
  34. 34. big meetings to decide how to provision new servers
  35. 35. 3-6 months (!!!!) turn around time
  36. 36. client tier logic tier data tier SQL
  37. 37. monolithic, 3-tier architectures
  38. 38. requires downtime for deployment
  39. 39. requires downtime for deployment (OK for businesses that aren’t 24/7)
  40. 40. big-bang releases
  41. 41. 2010
  42. 42. on premise cloud
  43. 43. EC2 EC2
  44. 44. EC2 EC2 months minutes
  45. 45. EC2 EC2 months minutes
  46. 46. EC2 EC2 minutes compute becoming a commodity Genesis Custom-built Product Commodity http://bit.ly/wardley-maps
  47. 47. EC2 EC2 minutes
  48. 48. users are distributed around the world systems have to be available 24/7
  49. 49. SCALABILITY
  50. 50. SCALABILITY RESILIENCE
  51. 51. SCALABILITY RESILIENCE SECURITY
  52. 52. SCALABILITY RESILIENCE SECURITY SPEED
  53. 53. Capex Opex capital expenditure operational expenditure
  54. 54. Capex Opex capital expenditure operational expenditure levelled the playing field
  55. 55. competition
  56. 56. competition user demand & expectations
  57. 57. faster delivery faster feedback loop we need…
  58. 58. big-bang releases small, frequent releases
  59. 59. co-evolution waterfall agile silos DevOps practice activity of and
  60. 60. scale
  61. 61. scale complexity
  62. 62. but our cognitive capacity hasn’t increased…
  63. 63. leverage: do more with less
  64. 64. EC2 EC2
  65. 65. EC2 EC2 we’re still managing infrastructure
  66. 66. https://bit.ly/2Im61VK “Unless you’re an infrastructure company, infrastructure is basically overhead.” Matt Klein
  67. 67. infrastructure you
  68. 68. EC2EC2 EC2 RDSDynamoDB SQS
  69. 69. Monoliths Microservices
  70. 70. EC2 EC2 EC2 DynamoDB EC2 RDS EC2 SQS DynamoDB
  71. 71. EC2 EC2 EC2 DynamoDB EC2 RDS EC2 SQS DynamoDB we’re managing lots more infrastructure!
  72. 72. we need a better abstraction for the “server”
  73. 73. we need an immutable infrastructure
  74. 74. 70% utilization monolith 10% utilization x 10 microservices
  75. 75. 70% utilization monolith 10% utilization x 10 microservices
  76. 76. 0 Theory “it works on my machine!” “production ready!”days
  77. 77. 0 Theory “it works on my machine!” “production ready!” 0 Reality “it works on my machine!” “production ready!” days days
  78. 78. mooooo..
  79. 79. runway
  80. 80. runway how do we optimize the runway to get more iterations out of it?
  81. 81. runway we need cheaper and lighter planes!
  82. 82. 2016
  83. 83. 2016
  84. 84. Server-ful Serverless
  85. 85. 2016 95% cost saving vs EC2
  86. 86. 2016 95% cost saving vs EC2 15x number of production deploys
  87. 87. 2016 95% cost saving vs EC2 15x number of production deploys same sized team
  88. 88. minimise undifferentiated heavy-lifting
  89. 89. Why serverless?
  90. 90. more Scalable
  91. 91. Cheaper (don’t pay for idle servers)
  92. 92. 2016 95% cost saving vs EC2
  93. 93. https://aws.amazon.com/solutions/case-studies/financial-engines/
  94. 94. https://www.doc.ic.ac.uk/~rbc/papers/fse-serverless-17.pdf “This paper presents two case industrial studies of early adopters, showing how migrating an application to the Lambda deployment architecture reduced hosting costs – by between 66% and 95%…”
  95. 95. Resilience (built-in redundancy and multi-AZ)
  96. 96. http://bit.ly/2Vzfexo
  97. 97. Secure
  98. 98. Shared Responsibility Model
  99. 99. protection from OS attacks Amazon automatically apply latest patches to host VMs
  100. 100. request blue-green deployment req/s auto-scaling us-east-1a us-east-1b us-east-1c multi-AZ
  101. 101. the DevOps forcethe DevOps force is strong with serverlessis strong with serverless
  102. 102. 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
  103. 103. 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
  104. 104. 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
  105. 105. idea production greater Velocity from idea to product
  106. 106. 2016 15x number of production deploys same sized team
  107. 107. leverage: do more with less
  108. 108. focus on customer needs
  109. 109. https://bit.ly/2Im61VK “Unless you’re an infrastructure company, infrastructure is basically overhead.” Matt Klein
  110. 110. building a resilient, and scalable infrastructure is hard work
  111. 111. building a resilient, and scalable infrastructure is hard work and crucial to your success!
  112. 112. diverts attention from core business problems
  113. 113. creates inter-team dependency
  114. 114. leading to delays, and time pressure and stress
  115. 115. serverless teams are smaller, and happier!
  116. 116. smaller teams less comm overhead fewer meetings more time getting stuff done!
  117. 117. developers are able to own more of their stack
  118. 118. developers are able to own more of their stack more autonomy
  119. 119. leverage: do more with less
  120. 120. cheaper, lighter, go faster
  121. 121. competition waits for no one

×