12.1.3 Dev Environment Parity

Dev environment parity is the degree to which a local development setup's overall behavior matches what an application will actually experience once deployed, an important consideration since a development environment that diverges too significantly from production risks letting issues go unnoticed until they unexpectedly surface later, in a more consequential context.

Why Some Divergence Between Dev and Production Is Expected and Reasonable

Certain differences — bind-mounted source code for fast iteration, exposed database ports for convenient local access — are reasonable, deliberate accommodations for development's different priorities, without meaningfully threatening overall parity.

services:
  db:
    ports:
      - "5432:5432"

This kind of difference is a reasonable development convenience, unlikely to cause an application to behave meaningfully differently in a way that matters for catching genuine issues.

Why Other Kinds of Divergence Are More Risky

Using a substantially different database version, a different underlying operating system base, or skipping dependencies entirely present in production risks an application behaving differently in ways that could mask a genuine, production-relevant issue.

services:
  db:
    image: postgres:13

If production actually runs PostgreSQL 16, this kind of version mismatch in development risks missing a behavior difference that would only actually surface once deployed against the real, different version.

Maintaining Reasonable Parity for Dependency Versions

Keeping a development environment's dependency versions reasonably aligned with production's actual versions reduces this specific risk.

services:
  db:
    image: postgres:16

Periodically Reviewing for Drift Between Dev and Production Configuration

As both environments evolve over time, periodically comparing their configurations helps catch any divergence that's crept in unintentionally, rather than only discovering it once it's already caused a production issue.

diff docker-compose.yml docker-compose.prod.yml

Why Dev Environment Parity Matters

Maintaining reasonable parity between development and production, while still allowing development-specific conveniences that don't meaningfully threaten that parity, is an important balance that helps ensure issues are more likely to be caught during development rather than first surfacing in production.