Tweet
Tweet

Slide 1

Slide 1 text

Serverless MythBusters Farrah Campbell & Danielle Heberling

Slide 2

Slide 2 text

Introduction Farrah Campbell Alliances & Ecosystem Director @FarrahC32 Danielle Heberling Software Engineer @deeheeber

Slide 3

Slide 3 text

Disclaimer The content in this presentation contains many anecdotes about our experiences with serverless that ultimately shaped our opinions — your experience and/or opinions might be different

Slide 4

Slide 4 text

Why Serverless? ● Scales for you when needed ● Lower liabilities: AWS operates the underlying infrastructure for you. ● You can ship faster with fewer people.

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

Cold Starts

Slide 7

Slide 7 text

Cold Starts - Anatomy of a Cold Start Load up code and modules Setup the function execution environment API call to invoke the function Run code

Slide 8

Slide 8 text

Cold Starts - Why is this a problem? ● An API endpoint that needs to be “always on” to receive requests ● Slow website

Slide 9

Slide 9 text

Fact or fiction??? Danielle’s take: Both

Slide 10

Slide 10 text

Cold Start - Mitigation ● Improved VPC Lambda networking ● Provisioned concurrency ● Have smaller package sizes ● Provision more memory

Slide 11

Slide 11 text

Lock In A. Purchase a product or service B. You’re stuck using them because everything you do is centered around vendor specific things

Slide 12

Slide 12 text

Lock - In Worries A. Vendor specific knowledge on the team B. What if cloud xyz all of a sudden decides to charge me more for using their managed services C. More difficult to switch to another cloud

Slide 13

Slide 13 text

Definition of Lock - In

Slide 14

Slide 14 text

Fact or fiction??? Farrah’s take: Fiction

Slide 15

Slide 15 text

Coupling & Tradeoffs “It’s coupling, not lock-in” - Yan Cui, May 2019

Slide 16

Slide 16 text

Some form of lock in is everywhere in software engineering.

Slide 17

Slide 17 text

Containers and Serverless Does Serverless replace containers?

Slide 18

Slide 18 text

Containers/Serverless — Comparison Container Services ● Always on ● Multi-platform ● Developer responsible for patching/updates ● Can run long processes Serverless Function ● Ephemeral ● Cloud provider specific ● Cloud provider does patching/updates ● Limited execution time

Slide 19

Slide 19 text

Fact or fiction??? Danielle’s take: Fiction

Slide 20

Slide 20 text

Why Not Both???

Slide 21

Slide 21 text

Use the right tool for the right job.

Slide 22

Slide 22 text

Containers/Serverless - Working Together ● Cloud Run ● Fargate ● Container image support for Lambda ● AWS SAM local invoke uses containers under the hood

Slide 23

Slide 23 text

Serverless is only for Greenfield Applications

Slide 24

Slide 24 text

Startups are finding success

Slide 25

Slide 25 text

It’s also for Legacy Applications

Slide 26

Slide 26 text

Legacy Migration Success MasterStream ● Modernizing applications into serverless architectures will reduce cost and unlock a range of cloud benefits. ● Drive a 90% reduction in the costs associated with managing traditional infrastructure required for monolithic applications. ● Increase engineering velocity by 60x in order to out-pace competitors.

Slide 27

Slide 27 text

Legacy Migration Success The business went from large queues of batch processes to real-time and from running on an AS/400 and Z-Series Mainframe to running a modern application using AWS Lambda and ECS.

Slide 28

Slide 28 text

Fact or fiction??? Farrah’s take: Fiction

Slide 29

Slide 29 text

More Stories of Legacy success Register of Scotland - 400 years of land deeds - reinvent talk 2020 Mphasis rearchitects a legacy application to a serverless cloud-native architecture on AWS Cedrus: Migrating a Legacy Application to a Serverless Ecosystem

Slide 30

Slide 30 text

What We Covered ● Cold Starts ● Vendor Lock In ● Containers and Serverless ● Serverless Application Success Stories

Slide 31

Slide 31 text

Thanks! @stackeryio @FarrahC32 @deeheeber