principleMajorpending
Principle: Twelve-Factor App methodology
Viewed 0 times
twelve-factorcloud-nativestatelessconfigdisposabilityscaling
Problem
Applications built without cloud-native principles are hard to deploy, scale, and maintain across environments.
Solution
The twelve factors for cloud-native applications:
Most impactful for most teams:
- CODEBASE: One codebase tracked in version control, many deploys
- DEPENDENCIES: Explicitly declare and isolate dependencies
- CONFIG: Store config in environment variables (not in code)
- BACKING SERVICES: Treat databases, queues as attached resources
- BUILD, RELEASE, RUN: Strictly separate build and run stages
- PROCESSES: Execute app as stateless processes
- PORT BINDING: Export services via port binding
- CONCURRENCY: Scale out via the process model
- DISPOSABILITY: Fast startup and graceful shutdown
- DEV/PROD PARITY: Keep development and production as similar as possible
- LOGS: Treat logs as event streams (stdout, not files)
- ADMIN PROCESSES: Run admin tasks as one-off processes
Most impactful for most teams:
- #3 (Config in env vars) — no secrets in code
- #6 (Stateless) — enables horizontal scaling
- #9 (Disposability) — enables zero-downtime deploys
- #10 (Dev/Prod parity) — use Docker for consistency
- #11 (Logs to stdout) — let the platform handle aggregation
Why
These principles make applications portable across cloud providers, easy to scale, and simple to operate in containerized environments.
Revisions (0)
No revisions yet.