#2SOURCEDEVELOP
Environment Separation
Clear dev/stage/prod boundaries
Easy
Overview
Strictly separated development, staging, and production environments. No shared databases or services.
Why It Matters
Prevents accidental prod changes. Each environment has its own config, data, and access controls.
The Risk
Shared environments mean mistakes in development can destroy production data. Without separation, there's no safe place to test destructive operations, schema changes, or load tests.
Implementation Components
A complete implementation of this capability includes:
- Separate infrastructure for dev, staging, and production
- Different credentials and API keys per environment
- Network isolation or firewall rules between environments
- Clear resource tagging (dev/stage/prod)
- Restricted access to production environment
- Separate databases with non-production using anonymized data
Implementation Pattern
- 1Create separate environments
- 2Use different credentials per env
- 3Isolate networks
- 4Tag resources clearly
- 5Restrict prod access
Tool Examples
These are examples, not endorsements. Choose what fits your context.
Dependencies
Enhanced by (more effective with)
Enables (unlocks)
Same Phase
Other capabilities in this pipeline phase