Difference between revisions of "Twelve-Factor App methodology (12F)"
Jump to navigation
Jump to search
(4 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | [[wikipedia:Twelve-Factor App methodology]] (12F) | + | [[wikipedia:Twelve-Factor App methodology]] (12F) (2011) methodology for building [[software-as-a-service]] applications. |
* https://12factor.net/ | * https://12factor.net/ | ||
+ | |||
+ | == The Twelve Factors == | ||
+ | {|class="wikitable" style=text-align:left | ||
+ | |+ The Twelve Factors<ref name="Red1"/><ref name="The12">{{cite web|last=Wiggins|first=Adam|title=The Twelve-Factor App|url=https://12factor.net/12factor.epub|access-date=21 December 2017|archive-url=https://web.archive.org/web/20170613060854/https://12factor.net/12factor.epub|archive-date=13 June 2017}}</ref> | ||
+ | ! # !! Factor !! Description | ||
+ | |- | ||
+ | | I || [[Codebase]] || There should be exactly one codebase for a deployed service with the codebase being used for many deployments. | ||
+ | |- | ||
+ | | II || [[Dependencies]] || All dependencies should be declared, with no implicit reliance on system tools or libraries. | ||
+ | |- | ||
+ | | III || [[Config]] || Configuration that varies between deployments should be stored in the environment. | ||
+ | |- | ||
+ | | IV || [[Backing services]]|| All backing services are treated as attached resources and attached and detached by the execution environment. | ||
+ | |- | ||
+ | | V || [[Build]], [[release]], [[run]] || The delivery pipeline should strictly consist of build, release, run. | ||
+ | |- | ||
+ | | VI || [[Processes]] || Applications should be deployed as one or more stateless processes with persisted data stored on a backing service. | ||
+ | |- | ||
+ | | VII || [[Port binding]] || Self-contained services should make themselves available to other services by specified ports. | ||
+ | |- | ||
+ | | VIII || [[Concurrency]] || Concurrency is advocated by scaling individual processes.<!-- Needs improvement but I am tied by WP:NOR --> | ||
+ | |- | ||
+ | | IX || [[Disposability]] || Fast startup and shutdown are advocated for a more robust and resilient system. | ||
+ | |- | ||
+ | | X || [[Dev]]/Prod [[parity]] || All environments should be as similar as possible. | ||
+ | |- | ||
+ | | XI || [[Logs]] || Applications should produce logs as event streams and leave the execution environment to aggregate. | ||
+ | |- | ||
+ | | XII || [[Admin Processes]] || Any needed admin tasks should be kept in source control and packaged with the application. | ||
+ | |} | ||
+ | |||
+ | == Related == | ||
+ | * [[Heroku]] | ||
== See also == | == See also == | ||
* {{APP}} | * {{APP}} | ||
+ | |||
+ | {{CC license}}. Source: wikipedia.com |
Latest revision as of 13:06, 10 November 2021
wikipedia:Twelve-Factor App methodology (12F) (2011) methodology for building software-as-a-service applications.
The Twelve Factors[edit]
# | Factor | Description |
---|---|---|
I | Codebase | There should be exactly one codebase for a deployed service with the codebase being used for many deployments. |
II | Dependencies | All dependencies should be declared, with no implicit reliance on system tools or libraries. |
III | Config | Configuration that varies between deployments should be stored in the environment. |
IV | Backing services | All backing services are treated as attached resources and attached and detached by the execution environment. |
V | Build, release, run | The delivery pipeline should strictly consist of build, release, run. |
VI | Processes | Applications should be deployed as one or more stateless processes with persisted data stored on a backing service. |
VII | Port binding | Self-contained services should make themselves available to other services by specified ports. |
VIII | Concurrency | Concurrency is advocated by scaling individual processes. |
IX | Disposability | Fast startup and shutdown are advocated for a more robust and resilient system. |
X | Dev/Prod parity | All environments should be as similar as possible. |
XI | Logs | Applications should produce logs as event streams and leave the execution environment to aggregate. |
XII | Admin Processes | Any needed admin tasks should be kept in source control and packaged with the application. |
Related[edit]
See also[edit]
- APP, Android, IOS, Frida, 12F, Amazon Honeycode, GitHub Apps, Heroku Review Apps, Bundle ID, APP ID, AWS AppConfig, TestFlight, Google Play Console, Apptopia
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy.. Source: wikipedia.com
- ↑ Cite error: Invalid
<ref>
tag; no text was provided for refs namedRed1
- ↑ Wiggins, Adam. "The Twelve-Factor App". Archived from the original on 13 June 2017. Retrieved 21 December 2017.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Advertising: