Loading content
The 12-Factor App model provides a structured approach to developing software applications that run in the cloud. It includes principles aimed at increasing the portability, scalability, and maintainability of applications. The 12 factors are: Codebase, Dependencies, Configuration, Backing Services, Build, Release, Run, Processes, Port Binding, Concurrency,…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
The Twelve-Factor App is a methodology for software-as-a-service applications that are intended to be deployed, operated, and scaled reliably. Twelve guidelines organize how teams handle code, dependencies, configuration, processes, and attached services.
The manifesto was written by Adam Wiggins and emerged from the environment of the Heroku platform. It distilled the contributors' experience developing, operating, and scaling numerous software-as-a-service applications into twelve broadly applicable solution principles.
Think of the application as a reproducible package that follows the same rules in many environments. One codebase produces multiple deploys; dependencies are explicitly declared, configuration comes from the environment, and persistent state lives in attached services. Build, release, and run remain separate stages, while stateless processes can be multiplied horizontally and logs flow outward as event streams.
One version-controlled codebase can run as separate deploys in multiple environments.
Environment-specific values are supplied outside the application code.
Running instances keep no durable local state, making them easier to replace or scale.
Databases, queues, and other services are treated as attached resources.
Creation, configuration, and execution form separate, traceable stages.
The methodology helps teams prepare portable deploys, automated delivery, and horizontal scaling. It is an operability guideline and does not replace a complete architecture, security, or observability strategy; modern platforms and containers add concrete practices around many factors.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.