The Twelve-Factor Function
summary
Argues that a twelve‑factor function separates meaning from magic so business rules are 100% meaningful and the rest is generic infrastructure. Demonstrates four core criteria: functions make outputs more valuable than inputs, must take arguments, must not reference deployment location, and must not reference persistence timing. Uses concrete examples (Postgres, Nginx, Kafka, Sequel, Rack), a 7.5 billion‑person matchmaking example, and claims decoupling yields smaller change footprints and faster iteration.
AI-written summary · about
chapters (6)
- 0:00Start
- 4:54finding meaning
- 5:41An example
- 6:17Another example
- 7:25Networks move information through space.
- 8:28Databases move information through time.
related talks
19mBuilding the Twelve-Factor App
34m7 Missing Factors for Your Production-Quality 12-Factor Apps
34m7 Missing Factors for Your Production-Quality 12-Factor Apps
42mThriving in the cloud: Going beyond the 12 factors
26mDevOps, 12-Factor, & Platform Engineering
31mThe 20 Year Platform – bringing together Kubernetes, 12-Factor and Functions
48mScale, Microservices and Flow
24mThe Future of Functions