The 12Factor App - Speaker Deck

Slide 1

Slide 1 text

@dmathieu Software Engineer @heroku The 12Factor App 1

Slide 2

Slide 2 text

Twelve Factor • Can apply to any language and platform! • Speeds up deployment! • Makes scaling easier! • Keeps apps clean 2

Slide 3

Slide 3 text

Let’s take a look 3

Slide 4

Slide 4 text

One codebase to rule them all 4

Slide 5

Slide 5 text

Codebase Production Staging Feature A Feature B 5

Slide 6

Slide 6 text

6 Multiple codebases is a distributed system

Slide 7

Slide 7 text

7 Create libraries

Slide 8

Slide 8 text

Explicitly declare and isolate dependencies 8

Slide 9

Slide 9 text

9 source 'https://rubygems.org' ! ruby '2.1.3' ! gem 'rails' gem 'pg' gem 'puma'

Slide 10

Slide 10 text

Slide 11

Slide 11 text

11 curl imagemagick

Slide 12

Slide 12 text

12 Config never goes in source control

Slide 13

Slide 13 text

Config Resource strings to databases Credentials to S3, Facebook, Twitter, … Security Tokens 13

Slide 14

Slide 14 text

$ cat .env! AWS_TOKEN=QWERTYUIOP! AWS_SECRET=12345 ! GITHUB_APP_ID=1! GITHUB_SECRET=67890 14

Slide 15

Slide 15 text

$ foreman run rails console! >> puts ENV[‘AWS_TOKEN’]! > “QWERTYUIOP” 15

Slide 16

Slide 16 text

You can use a yml config file* *Just don’t store it in source control

Slide 17

Slide 17 text

Treat backing services as attached resources 17

Slide 18

Slide 18 text

18 DATABASE_URL= postgres://example.com:5032

Slide 19

Slide 19 text

Production deploy PostgreSQL Email Service Amazon S3

Slide 20

Slide 20 text

20 One codebase per app Explicitly declare and isolate dependencies Don’t put config in source control Treat backing services as attached resources

Slide 21

Slide 21 text

Build Release Run 21

Slide 22

Slide 22 text

Codebase Build Run Config 22

Slide 23

Slide 23 text

Codebase Build Run Config 23

Slide 24

Slide 24 text

Execute the app as one or more stateless processes 24

Slide 25

Slide 25 text

web.1 web.2 Database 25

Slide 26

Slide 26 text

26 No sticky sessions

Slide 27

Slide 27 text

27 Ephemeral filesystem

Slide 28

Slide 28 text

28 Export services via port binding

Slide 29

Slide 29 text

29 Self-contained app

Slide 30

Slide 30 text

30 An app can be the backing service for an other

Slide 31

Slide 31 text

Scale out via the process model 31

Slide 32

Slide 32 text

web.1 web.2 web.3 worker.1 worker.2 clock.1 32

Slide 33

Slide 33 text

33 You can still do your own internal multiplexing

Slide 34

Slide 34 text

34 Build, release, run One or more stateless processes Scale out via the process model Export services via port binding

Slide 35

Slide 35 text

Maximize robustness with fast startup and graceful shutdown 35

Slide 36

Slide 36 text

36 Handle a request

Slide 37

Slide 37 text

37 60s to boot is a lot

Slide 38

Slide 38 text

38 Use the SIGTERM signal

Slide 39

Slide 39 text

39 Send jobs back to the queue

Slide 40

Slide 40 text

40 Build, release, run One or more stateless processes Scale out via the process model Fast startup

Slide 41

Slide 41 text

Keep development, staging, and production as similar as possible 41

Slide 42

Slide 42 text

42 Use the same kind of machine

Slide 43

Slide 43 text

43 With the same OS version

Slide 44

Slide 44 text

44 And the same database server

Slide 45

Slide 45 text

Logging 45

Slide 46

Slide 46 text

46 Production errors will happen

Slide 47

Slide 47 text

47 Tail logs to find the cause

Slide 48

Slide 48 text

48 Then use a logging service to dig in deeper

Slide 49

Slide 49 text

action=create_user [email protected] action=log_user [email protected] 49

Slide 50

Slide 50 text

count#api-call-200=1 50

Slide 51

Slide 51 text

Don’t write logs to a file 51

Slide 52

Slide 52 text

Run admin/ management tasks as one-off processes 52

Slide 53

Slide 53 text

53 Not in your app’s main processes

Slide 54

Slide 54 text

54 Run console instances the same way

Slide 55

Slide 55 text

55 Keep all your environments as similar as possible Run management tasks as one-off processes Logging

Slide 56

Slide 56 text

Do you like? • Minimizing new developer overhead?! • Running in multiple environments?! • Easily scaling without tooling, architecture or development headaches?! • Having the latest update available to users at a moments notice? Read more at 12factor.net 56

Slide 57

Slide 57 text

Questions? [email protected] 12factor.net 57 @dmathieu