the twelve-factor app, one line each

12factor.net's own wording, trimmed to a single line per factor

Codebase - one codebase tracked in revision control, many deploys

one repo, deployed to as many environments as you want. simple rule, still gets violated at real jobs constantly

Dependencies - explicitly declare and isolate dependencies

Config - store config in the environment

the one everyone quotes. env vars, not a config file checked into git. you will look this up again the first time you leak a key

Backing services - treat backing services as attached resources

Build, release, run - strictly separate build and run stages

sounds obvious until you've worked somewhere that ssh's into prod and edits a file live

Processes - execute the app as one or more stateless processes

Port binding - export services via port binding

Concurrency - scale out via the process model

Disposability - maximize robustness with fast startup and graceful shutdown

matters most once you're on anything that autoscales or restarts containers on its own

Dev/prod parity - keep development, staging, and production as similar as possible

docker made most of this free. read the docs from before containers were normal and appreciate how bad it used to be

Logs - treat logs as event streams

Admin processes - run admin/management tasks as one-off processes

migrations, one-off scripts, console sessions. same codebase and config as the app, not a special snowflake box

Or start a list of your own. Free, it takes a minute.

Related lists