Difference between revisions of "Twelve-Factor App methodology (12F)"

From wikieduonline
Jump to navigation Jump to search
 
(One intermediate revision by the same user not shown)
Line 9: Line 9:
 
! # !! Factor !! Description
 
! # !! Factor !! Description
 
|-
 
|-
−
| I || Codebase || There should be exactly one codebase for a deployed service with the codebase being used for many deployments.
+
| 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.
+
| 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.
+
| 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.
+
| 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.
+
| 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.
+
| 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.
+
| 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 -->
+
| 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.
+
| 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.
+
| 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.
+
| 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.
+
| XII || [[Admin Processes]] || Any needed admin tasks should be kept in source control and packaged with the application.
 
|}
 
|}
−
 
−
 
  
 
== Related ==
 
== Related ==
Line 42: Line 40:
 
* {{APP}}
 
* {{APP}}
  
−
{{CC license}}
+
{{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]

The Twelve Factors[1][2]
# 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]

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

  1. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Red1
  2. ↑ 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>
Retrieved from "https://www.wikieduonline.com/index.php?title=Twelve-Factor_App_methodology_(12F)&oldid=99485"

Advertising: