A thorough review of the Twelve-Factor App methodology, 15 years after its creation at Heroku. Each of the twelve factors is examined in the context of modern cloud-native development — containers, Kubernetes, serverless, GitOps, and AI workloads. Most factors hold up well and have become default practice; a few show their age (port binding for serverless, env vars as the only config mechanism, logs vs. full observability). The post also adds a 13th consideration not in the original: backward and forward compatibility during rolling deployments, covering database schemas, API contracts, cached data, and event schemas.

19m read timeFrom itnext.io
Post cover image
Table of contents
I. CodebaseII. DependenciesIII. ConfigIV. Backing ServicesV. Build, Release, RunVI. ProcessesVII. Port BindingGet Lukas Niessen ’s stories in your inboxVIII. ConcurrencyIX. DisposabilityX. Dev/Prod ParityXI. LogsXII. Admin ProcessesBeyond the Twelve: Forward and Backward CompatibilityWrapping Up

Sort: