Please enable JavaScript.
Coggle requires JavaScript to display documents.
The Twelve-Factor Methodology (Principle 2: Dependencies (Explicitly…
The Twelve-Factor Methodology
Principle 1) Codebase
Must be tracked in version control
Will have many deploys
Principle 2: Dependencies
Explicitly declared and isolated
Consider using reusable functions or share as a library
Use dependency management tools to share libraries
Principle 3: Configuration
Configuration should never go into the source code
Configurations should be stored as part of the environment
Configuration file
Environment variable
Principle 4: Backing Services
Treat backing servics as an attached resource
Treat services the same way, whether it's an internal database or third-party service
Should be easy to deploy and change
Principle 5: Build, Release, Run
Always have a build and deploy strategy
Build strategies for repeatable builds, versioning of running system, and rollback
Principle 6: Processes
Execute the application as one or more stateless process
Sticky sessions need to revisited and re-implemented
Might be challenging in large enterprise with architecture already in place
Principle 7: Port Binding
Expose service via port binding
Principles 8 Concurrency
Scale out with the process model
Principle 9: Disposability
Quick application startup and shutdown times
Principle 10: Dev/prod parity
Application works the same way in dev, staging, and production
Principle 11: Log management
Treat log as an event stream
Principle 12: Admin tasks
Treat the same way like the rest of the application
Run against a release and ship alongside the code to avoid versioning issue