12-Factor App Methodology

The 12-Factor App methodology is a set of principles for building cloud-native applications that are portable, scalable, and maintainable. Originally articulated by Heroku co-founder Adam Wiggins, these factors address codebase management, dependency declaration, configuration externalization, backing service abstraction, build/release/run separation, stateless processes, port binding, concurrency via process model, disposability, dev/prod parity, log streaming, and admin process management.

In practice, adhering to these factors means using a single codebase tracked in version control, explicitly declaring all dependencies (no implicit system-level dependencies), storing config in the environment, treating databases, caches, and message queues as attached resources swappable via URL changes, building immutable release artifacts, running stateless processes that store session data in external stores, and scaling horizontally by adding process instances rather than scaling vertically.

The methodology promotes applications that start up fast and shut down gracefully (disposability), maintain minimal divergence between development and production environments (dev/prod parity), treat logs as unbuffered event streams routed to external aggregators, and run administrative tasks as one-off processes using the same codebase and config. While originally targeted at PaaS deployments, these principles remain foundational for containerized and serverless architectures.