Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
The Twelve-Factor App
Search
Kristian Glass
September 20, 2014
Programming
2
1.1k
The Twelve-Factor App
http://12factor.net/
- what, why, how
From PyCon UK 2014
Kristian Glass
September 20, 2014
Tweet
Share
More Decks by Kristian Glass
See All by Kristian Glass
How To Screw Up Hiring - Kristian Glass - PyCon UK 2018
doismellburning
0
410
Infrastructure as Code with AWS CloudFormation and Sceptre
doismellburning
0
3.6k
Other Decks in Programming
See All in Programming
Taking LLMs out of the black box: A practical guide to human-in-the-loop distillation
inesmontani
PRO
3
1.1k
AWS CDKを用いたセキュアなCI/CDパイプラインの構築 / Build a secure CI/CD pipeline using AWS CDK
seike460
PRO
3
590
NANIMACHI
naokiito
0
940
色んなオートローダーを覗き見る #phpcon_okinawa
o0h
PRO
5
370
実践Dash - 手を抜きながら本気で作るデータApplicationの基本と応用 / Dash for Python and Baseball
shinyorke
2
250
Vue :: Better Testing 2024
up1
1
380
XP2024 っていう国際会議に行ってきたよの記 / XP2024 Conference Report
bonotake
4
200
The Efficiency Paradox and How to Save Yourself and the World
hollycummins
0
160
◯◯エンジニアになった理由
gessy0129
PRO
0
630
The Myth of the Modular Monolith - Day 2 Keynote - Rails World 2024
eileencodes
6
260
Remix × Cloudflare Pages × Sentry 奮闘記 / remix-pages-sentry
nkzn
1
390
クラウドサービスの 利用コストを削減する技術 - 円安の真南風を感じて -
pyama86
3
250
Featured
See All Featured
4 Signs Your Business is Dying
shpigford
180
21k
Writing Fast Ruby
sferik
625
60k
StorybookのUI Testing Handbookを読んだ
zakiyama
26
5.1k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
28
9k
Teambox: Starting and Learning
jrom
131
8.7k
Build The Right Thing And Hit Your Dates
maggiecrowley
31
2.3k
How STYLIGHT went responsive
nonsquared
94
5.1k
Embracing the Ebb and Flow
colly
83
4.4k
Documentation Writing (for coders)
carmenintech
65
4.3k
How to Think Like a Performance Engineer
csswizardry
16
1k
A Philosophy of Restraint
colly
202
16k
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
191
16k
Transcript
The Twelve-Factor App Kristian Glass @doismellburning http://www.doismellburning.co.uk/talks/django12factor 1
•I do development •I do operations •I write code and
care how it runs 2
What is Twelve Factor? “A methodology for building web apps”
3
Core Concept Clean interface between app and underlying system 4
#1 One code repository, many deploys 5
#2 Explicitly declare and isolate dependencies 6
So, virtualenv and requirements.txt ? 7
$ pip install -r requirements.txt! # …! Downloading/unpacking gevent! Running
setup.py egg_info for package gevent! # …! gevent/libevent.h:9:19: error: event.h: No such file or directory! # …! error: command 'gcc-4.2' failed with exit status 1 8
So how? •Containers/VMs •OS packages (ish) 9
#3 Read config from the environment 10
What is Config? Everything likely to vary between deploys 11
Config Examples •Service URLs (Database, mail, etc.) •Service credentials •Debug
flag 12
Why do this? •Separation of responsibility •Language and framework independent
•Avoid leakage of secrets 13
But config files? •Apps read from environment •Environment may come
from files 14
How do I populate the environment? • foreman • honcho
• envdir • supervisor • bash scripts • and more… 15
Using Django? https://github.com/doismellburning/ django12factor 16
#4 Treat backing services as attached resources 17
Attached Resources •No distinction between local/external resources •Loose coupling 18
#5 Distinct build/ release/run stages 19
Build / Release? build :: Code -> Executable! ! release
:: Config -> Executable -> Release Artefact 20
Example: Building a Django Project $ git clone! $ virtualenv!
$ pip install -r requirements.txt! $ manage.py collectstatic ! $ fpm 21
Releases •New config? New release •New code? New build, new
release 22
Run stage As simple as possible 23
Why? •Do hard work in advance •Optimise the common case
24
#6 Run as stateless process(es) 25
Stateless Processes •Persist data to external services •Assume nothing about
RAM/ disk •No sticky sessions 26
#7 Export services via port binding 27
What does this mean? •Your app should offer its services
by some protocol on some port •Self-contained services: run and go 28
#8 Scale out with processes 29
Process model •More load? More processes •Background jobs? Worker processes
•Don’t daemonise, that’s manager’s job 30
#9 Start quickly, stop nicely 31
Start quickly, stop nicely •Disposable apps •Auto-scale easily •Deploy quickly
and easily 32
#10 Keep environments as similar as possible 33
Three prod/dev gaps •Time gap •People gap •Tools gap 34
Time gap •“Production is weeks behind dev” •Solution: Deploy more
35
People gap •“Developers write code, Ops run it” •Solution: DevOps
36
Tool gap •“It works on my machine” •Solution: Use the
same tools everywhere 37
#11 Treat logs as event streams 38
Logs as event streams •No logfile / routing / storage
handling •Spit logs out to stdout •One event, one line 39
#12 Admin tasks as part of your app 40
What does that mean? •Django management commands are a great
example •$ python manage.py syncdb! •No private folders of “useful snippets” •Keep them with the app 41
Recap 1. One codebase 2. Dependencies 3. Config in environment
4. Backing Services 5. Build, release, run 6. Stateless processes 7. Port binding 8. Scale with processes 9. Disposability 10. Dev/prod parity 11. Logs as event stream 12. Admin processes 42
Recap •It does not matter what language •It does not
matter what framework 43
Questions? http://www.doismellburning.co.uk/talks/django12factor 44