@mattab opened this Issue on September 16th 2014 Member

The Twelve-Factor App is a methodology for building software-as-a-service apps. The goal of this issue is to read and analyse Piwik from the point of view of the twelve-factor methodology and see if we comply, or which areas could be improved. The outcome should be a list of thoughts and maybe issues created in order to improve the Saas platform.

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

Who should read this document?
Any developer building applications which run as a service. Ops engineers who deploy or manage such applications.

-> Learn more: http://12factor.net/

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

Refs #6197

Feel free to post your thoughts and comments!

Powered by GitHub Issue Mirror