DevProdParity [principle] v1.0.0

Keep development, staging, and production as similar as possible across three gaps: time (deploy hourly, not quarterly), personnel (the developer who wrote the code deploys it), and tools (same DB, same queue, same OS — not SQLite locally and Postgres in prod).

Close the gap between dev and prod on time, people, and tools.

Applies To

• Run prod-equivalent backing services locally via containers — not lightweight stand-ins.
• Continuous deployment narrows the time gap; daily deploys beat quarterly releases.
• Same engineer authors and watches the deploy. No throw-it-over-the-wall to ops.

DevProdParity [principle] v1.0.0

Keep development, staging, and production as similar as possible across three gaps: time (deploy hourly, not quarterly), personnel (the developer who wrote the code deploys it), and tools (same DB, same queue, same OS — not SQLite locally and Postgres in prod).

Close the gap between dev and prod on time, people, and tools.

Applies To

• Run prod-equivalent backing services locally via containers — not lightweight stand-ins.
• Continuous deployment narrows the time gap; daily deploys beat quarterly releases.
• Same engineer authors and watches the deploy. No throw-it-over-the-wall to ops.

Relations

requires: [@backend-architecture/principle-dependencies-explicit]

Requires

• @backend-architecture/principle-dependencies-explicit