Slide 1

Slide 1 text

You shall not FaaS Manuela Rink Software Engineer @

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

FaaS You shall not

Slide 4

Slide 4 text

Love at first sight! But then…

Slide 5

Slide 5 text

Did it hurt when... ... you created a "at least it does it's job" thing ... and then said "Nah" [ things happened ] ... did things your common way? [ no profit ] http://4.bp.blogspot.com/-GyHYgJ89IPM/UdUMR4XyAjI/AAAAAAAAJEc/uMw6_Pqqrs8/s570/02-words_add_meaning_to_pictures.jpg

Slide 6

Slide 6 text

Said it’s just not ready yet… ... when you created a thing [ things happened ] ... and instantly deleted it? [ no profit ] http://favoritememes.com/_nw/88/84578727.jpg

Slide 7

Slide 7 text

You started hating it when… ... you missed something during development [ things happened ] ... and burned a serious amout of money? [ no profit ] http://iruntheinternet.com/lulzdump/images/science-wizard-burning-money-dollars-14189000382.jpg

Slide 8

Slide 8 text

https://sourcebox.be/blog/2017/08/07/serverless-a-lesson-learned-the-hard-way/ 2 weeks vacation Current $ 5 Forecast $ 83 Current $ 180 Forecast $ 800 Update calc cache duration write metadata blob change activated The ~$200 return!

Slide 9

Slide 9 text

What you need to know…

Slide 10

Slide 10 text

Jeff is NOT… the holy grail to system architecture http://www.thecooltshirt.com/wp-content/uploads/2015/01/qwertee_banksypython125.jpg

Slide 11

Slide 11 text

Jeff is NOT… a fluffy tool to solve all design & architecture problems http://cdn7.viralscape.com/wp-content/uploads/2015/04/Flying-Cat-19.jpg

Slide 12

Slide 12 text

Jeff will NOT… help reduce your system’s complexity magically in fact you might even make it worse https://imgflip.com/

Slide 13

Slide 13 text

Serverless is… a software engineering pattern …not more and not less https://imgflip.com/

Slide 14

Slide 14 text

https://imgflip.com/ A quick guide

Slide 15

Slide 15 text

Example A: Copy & Paste to Serverless Production System Let’s call it legacy “Future proof” System You needed to rewrite “a lot” anyway

Slide 16

Slide 16 text

Example B: The Green Field - $everything serverless Brand new $all serverless Just … because reasons!

Slide 17

Slide 17 text

Example C: The Agile “Let’s see” approach Agile System If it’s not good, it isn’t done yet

Slide 18

Slide 18 text

And the guide? https://imgflip.com/

Slide 19

Slide 19 text

Serverless is… Stateless Loosely coupled Fully managed Auto scaled Pay what you use

Slide 20

Slide 20 text

Architecture Latency Consistency Availability Need for State Costs o Usage o Memory need o Your budget? o Again: Architecture! Think about…

Slide 21

Slide 21 text

Consumption Plan “pay what you use” dynamic auto scale App Service Plan “my fixed resources” planned scaling

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

“Shall I FaaS” aka Helping Diagram “Will Jeff and I be a good fit?”

Slide 24

Slide 24 text

Merci :) Manu Rink Technical Evangelist [email protected] @codeprincess says