Meta tags:
description= A methodology for building modern, scalable, maintainable software-as-a-service apps.;
author= Adam Wiggins;
Headings (most frequently used words):
as, the, processes, and, services, run, one, twelve, app, codebase, dependencies, config, backing, build, port, binding, logs, admin, in, treat, via, factor, introduction, background, who, should, read, this, document, factors, ii, iii, iv, release, vi, vii, viii, concurrency, ix, disposability, dev, prod, parity, xi, xii, tracked, revision, control, many, deploys, explicitly, declare, isolate, store, environment, attached, resources, strictly, separate, stages, execute, or, more, stateless, export, scale, out, process, model, maximize, robustness, with, fast, startup, graceful, shutdown, keep, development, staging, production, similar, possible, event, streams, management, tasks, off,
Text of the page (most frequently used words):
the (23), and (16), for (8), #development (7), app (7), service (6), apps (6), #twelve (5), software (5), run (4), processes (4), services (4), factor (4), one (3), with (3), via (3), backing (3), codebase (3), any (3), this (3), document (3), our (3), problems (3), modern (3), between (3), deployment (3), privacy (2), salesforce (2), all (2), written (2), admin (2), treat (2), logs (2), production (2), scale (2), port (2), binding (2), build (2), config (2), dependencies (2), building (2), applications (2), which (2), who (2), application (2), those (2), architecture (2), practices (2), dynamics (2), time (2), developers (2), cost (2), have (2), hundreds (2), methodology (2), can (2), use (2), maximum (2), minimize (2), cookie, preferences, your, choices, contact, trust, responsible, disclosure, information, terms, legal, copyright, 2026, inc, rights, reserved, various, trademarks, held, their, respective, owners, tower, 415, mission, street, 3rd, floor, san, francisco, 94105, united, states, adam, wiggins, last, updated, 2017, download, epub, book, sourcecode, 简体中文, zh_cn, tiếng, việt, українська, türkçe, ภาษาไทย, slovensky, русский, português, brasil, pt_br, polski, 한국어, 日本語, italiano, français, فارسی, español, english, ελληνικά, deutsch, česky, management, tasks, off, xii, event, streams, keep, staging, similar, possible, dev, prod, parity, maximize, robustness, fast, startup, graceful, shutdown, disposability, out, process, model, viii, concurrency, export, vii, execute, more, stateless, strictly, separate, stages, release, attached, resources, store, environment, iii, explicitly, declare, isolate, tracked, revision, control, many, deploys, factors, developer, ops, engineers, deploy, manage, such, should, read, motivation, raise, awareness, some, systemic, seen, provide, shared, vocabulary, discussing, offer, set, broad, conceptual, solutions, accompanying, terminology, format, inspired, martin, fowler, books, refactoring, patterns, enterprise, synthesizes, experience, observations, wide, variety, wild, triangulation, ideal, paying, particular, attention, organic, growth, over, collaboration, working, avoiding, erosion, contributors, been, directly, involved, indirectly, witnessed, operation, scaling, thousands, work, platform, heroku, background, applied, programming, language, combination, database, queue, memory, cache, etc, without, significant, changes, tooling, enabling, agility, continuous, divergence, are, suitable, obviating, need, servers, systems, administration, cloud, platforms, underlying, operating, system, offering, execution, environments, portability, clean, contract, formats, setup, automation, new, joining, project, declarative, era, commonly, delivered, called, that, web, introduction, github, community, blog,
Text of the page (random words):
the twelve factor app the twelve factor app blog community github introduction in the modern era software is commonly delivered as a service called web apps or software as a service the twelve factor app is a methodology for building software as a service apps that use declarative formats for setup automation to minimize time and cost for new developers joining the project have a clean contract with the underlying operating system offering maximum portability between execution environments are suitable for deployment on modern cloud platforms obviating the need for servers and systems administration minimize divergence between development and production enabling continuous deployment for maximum agility and can scale up without significant changes to tooling architecture or development practices the twelve factor methodology can be applied to apps written in any programming language and which use any combination of backing services database queue memory cache etc background the contributors to this document have been directly involved in the development and deployment of hundreds of apps and indirectly witnessed the development operation and scaling of hundreds of thousands of apps via our work on the heroku platform this document synthesizes all of our experience and observations on a wide variety of software as a service apps in the wild it is a triangulation on ideal practices for app development paying particular attention to the dynamics of the organic growth of an app over time the dynamics of collaboration between developers working on the app s codebase and avoiding the cost of software erosion our motivation is to raise awareness of some systemic problems we ve seen in modern application development to provide a shared vocabulary for discussing those problems and to offer a set of broad conceptual solutions to those problems with accompanying terminology the format is inspired by martin fowler s books patterns of enterprise application architecture and refactoring who should read this document any developer building applications which run as a service ops engineers who deploy or manage such applications the twelve factors i codebase one codebase tracked in revision control many deploys ii dependencies explicitly declare and isolate dependencies iii config store config in the environment iv backing services treat backing services as attached resources v build release run strictly separate build and run stages vi processes execute the app as one or more stateless processes vii port binding export services via port binding viii concurrency scale out via the process model ix disposability maximize robustness with fast startup and graceful shutdown x dev prod parity keep development staging and production as similar as possible xi logs treat logs as event streams xii admin processes run admin management tasks as one off processes česky cs deutsch de ελληνικά el english en español es فارسی fa français fr italiano it 日本語 ja 한국어 ko polski pl português do brasil pt_br русский ru slovensky sk ภาษาไทย th türkçe tr українська uk tiếng việt vi 简体中文 zh_cn written by adam wiggins last updated 2017 sourcecode download epub book copyright 2026 salesforce inc all rights reserved various trademarks held by their respective owners salesforce tower 415 mission street 3rd floor san francisco ca 94105 united states legal terms of service privacy information responsible disclosure trust contact your privacy choices cookie preferences
|
