DEFINE: Twelve-Factor App methodology | Research & Refine

[iPoetDev]

[DEFINE](): Inspect and Refine: 12 Factor App as Methodology for defining software as a service (i.e. web apps) as needed.

PROJECT | SOLUTION: Concept | Idea Capture | Discovery | Document Driven Effort

• Ideation, Concept
• Research
• Readme
  • Writing
  • Diagramming
• Proofing
• Editorial

Idea

• Architecture: 12 Factor Methodology
• Theme: Defining approach to Software as a Service delivery

As a developer, 
investigate if the declarative format and having clean contracts is
suitable for deployments to cloud platforms 
and to mimimise divergence between development and production 
by enabling continuous deployment for maximum agility.

Audience:

• Any developer building applications which run as a service
• Ops engineers who deploy or manage such applications.

Research

Sources

• https://12factor.net/
• https://en.wikipedia.org/wiki/Twelve-Factor_App_methodology
• Heroku defined in 2011
• The twelve factors are however cited as a baseline from which to adapt or extend ("Beyond the Twelve-Factor App - Exploring the DNA of Highly Scalable, Resilient Cloud Applications". O'Reilly)

Select Attributes of 12 Factor Apps

1. Select the Factors that are just enough fit/right size for the assessment criteria
2. Scope the Factors that are just beyond the right size for the asssement criteria
3. Exclude the Factor that are excessively beyond the scope of the assessment criteria

Platform (Software) as a Service

• Context: Django Web App
• Hosting: Heroku Cloud PaaS HostingPlatform
• Reference: Twelve-Factor Methodology Applied to a Django App

1. Selected / Required
   • 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
   • [XII. Admin processes] (https://12factor.net/admin-processes): Run admin/management tasks as one-off processes
2. Scope In/Out? or Once Off
   • V. Build, release, run: Strictly separate build and run stages
   • X. Dev/prod parity: Keep development, staging, and production as similar as possible
   • XI. Logs: Treat logs as event streams
3. Exclude/Implicit Design for Django Context:
   • No links
   • VI. Processes
   • VII. Port binding
   • VIII. Concurrency
   • IX. Disposability

Readme

• Header:
• Tags:
• Notes:

Proof

Grammar, Spelling, Diagram,

Editorial

• Include
• Edit
• Exclude