CI/CD · Ship safely, repeatedly
How should staging differ from production?
Short answer
Staging should mirror the production architecture, deployment method and configuration shape, but use synthetic data and smaller scale. Every difference should be deliberate because differences hide production failures.
Staging is valuable when it can reproduce production behaviour closely enough to catch integration, configuration and migration problems. A staging environment with a different database engine or deployment mechanism gives false confidence.
- Keep the same runtime versions, service topology and infrastructure primitives
- Use the same deployment pipeline and configuration keys, with different values
- Use synthetic or anonymized data, never copy raw production personal data
- Scale down where cost requires it, but document which tests depend on scale
- Test migrations and rollback in staging before production
services:
api:
image: registry.example.com/api:1.8.3
replicas: 2
database:
engine: postgres
version: 16
data: syntheticFollow-ups you should expect
Interviewers use these to check whether the first answer was understanding or memorisation.
- 1What differences between staging and production are acceptable?
- 2How do you test a database migration safely?
- 3Can preview environments replace staging?
- 4What do you do when staging is down?
Say it in the interview
Staging should match production in architecture, runtime versions and deployment method, while using synthetic data and reduced scale. I keep the configuration keys identical but inject different values. The differences I accept are cost-driven and documented. If staging drifts or is routinely broken, I would rather fix it or replace it with reliable preview and post-deploy checks than pretend it provides safety.
Use this as a model, not a script. Saying it in your own words is what makes it survive follow-up pressure.
Related questions
Reading is step one
Now say it out loud.
Understanding an answer and delivering it under pressure are different skills. Rehearse this topic in a live CI/CD mock interview and get scored feedback on depth, clarity and confidence.