{"topic":{"id":11572,"title":"The Twelve-Factor App","slug":"topic","userId":1047,"categoryId":4,"createdAt":"2024-04-20 03:01:59.184194","bumpedAt":"2024-04-20 03:01:59.296037","views":208,"postsCount":1,"highestPostNumber":1,"likeCount":0,"closed":false,"pinned":false,"pinnedGlobally":false,"pinnedAt":null,"pinnedUntil":null,"isBanner":false,"excerpt":"https://www.12factor.net/ The Twelve-Factor App 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…","deletedAt":null,"isAnonymous":false,"isPrivate":false,"isMembersOnly":false,"category":{"id":4,"name":"谈笑风生","slug":"general","color":"25AAE2"},"author":{"id":1047,"username":"anonymous_coward_old","name":"Anonymous Coward Old","avatarUrl":"/uploads/image/43/32/4332638c11248b8ff07033c11de0759a55205facfbec85e14458245a91991faf.avif"},"realAuthor":{"id":1047,"username":"anonymous_coward_old","name":"Anonymous Coward Old","avatarUrl":"/uploads/image/43/32/4332638c11248b8ff07033c11de0759a55205facfbec85e14458245a91991faf.avif"},"tags":[]},"posts":[{"id":30186,"postNumber":1,"raw":"https://www.12factor.net/\r\n\r\n\r\n\r\nThe Twelve-Factor App\r\nIntroduction\r\n\r\nIn 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:\r\n\r\n Use declarative formats for setup automation, to minimize time and cost for new developers joining the project;\r\n Have a clean contract with the underlying operating system, offering maximum portability between execution environments;\r\n Are suitable for deployment on modern cloud platforms, obviating the need for servers and systems administration;\r\n Minimize divergence between development and production, enabling continuous deployment for maximum agility;\r\n And can scale up without significant changes to tooling, architecture, or development practices.\r\n\r\nThe 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).\r\nBackground\r\n\r\nThe 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.\r\n\r\nThis 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.\r\n\r\nOur 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.\r\nWho should read this document?\r\n\r\nAny developer building applications which run as a service. Ops engineers who deploy or manage such applications.\r\nThe Twelve Factors\r\nI. Codebase\r\nOne codebase tracked in revision control, many deploys\r\nII. Dependencies\r\nExplicitly declare and isolate dependencies\r\nIII. Config\r\nStore config in the environment\r\nIV. Backing services\r\nTreat backing services as attached resources\r\nV. Build, release, run\r\nStrictly separate build and run stages\r\nVI. Processes\r\nExecute the app as one or more stateless processes\r\nVII. Port binding\r\nExport services via port binding\r\nVIII. Concurrency\r\nScale out via the process model\r\nIX. Disposability\r\nMaximize robustness with fast startup and graceful shutdown\r\nX. Dev/prod parity\r\nKeep development, staging, and production as similar as possible\r\nXI. Logs\r\nTreat logs as event streams\r\nXII. Admin processes\r\nRun admin/management tasks as one-off processes","cooked":"\n

The Twelve-Factor App
\nIntroduction

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;\nHave a clean contract with the underlying operating system, offering maximum portability between execution environments;\nAre suitable for deployment on modern cloud platforms, obviating the need for servers and systems administration;\nMinimize divergence between development and production, enabling continuous deployment for maximum agility;\nAnd can scale up without significant changes to tooling, architecture, or development practices.\n

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).
\nBackground

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.
\nWho should read this document?

Any developer building applications which run as a service. Ops engineers who deploy or manage such applications.
\nThe Twelve Factors
\nI. Codebase
\nOne codebase tracked in revision control, many deploys
\nII. Dependencies
\nExplicitly declare and isolate dependencies
\nIII. Config
\nStore config in the environment
\nIV. Backing services
\nTreat backing services as attached resources
\nV. Build, release, run
\nStrictly separate build and run stages
\nVI. Processes
\nExecute the app as one or more stateless processes
\nVII. Port binding
\nExport services via port binding
\nVIII. Concurrency
\nScale out via the process model
\nIX. Disposability
\nMaximize robustness with fast startup and graceful shutdown
\nX. Dev/prod parity
\nKeep development, staging, and production as similar as possible
\nXI. Logs
\nTreat logs as event streams
\nXII. Admin processes
\nRun admin/management tasks as one-off processes

\n","createdAt":"2024-04-20 03:01:59.296037","updatedAt":"2024-04-20 03:01:59.296037","replyToPostNumber":null,"replyCount":0,"likeCount":0,"wordCount":421,"liked":false,"bookmarked":false,"polls":[],"reactions":[],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"isAnonymous":false,"user":{"id":1047,"username":"anonymous_coward_old","name":"Anonymous Coward Old","avatarUrl":"/uploads/image/43/32/4332638c11248b8ff07033c11de0759a55205facfbec85e14458245a91991faf.avif","admin":false,"moderator":false,"signatureRaw":null,"signatureCooked":null}}],"hasMore":false,"lastReadPostNumber":1,"hasUrlPostNumber":false}