Understanding declarative normalizer in production (#534)

Testing in Production

Yes, you read that right. Testing in production — not instead of staging, but in addition to it. Here's why and how.

Why Staging Lies

Staging environments differ from production in subtle but critical ways:

  • Different data volumes (10K rows vs 10M rows)
  • Different traffic patterns (no real users)
  • Different infrastructure (smaller instances)
  • Different integrations (sandbox APIs)

Canary Deployments

Route a small percentage of traffic to the new version:

# nginx.conf
upstream backend {
    server app-v1:8080 weight=95;
    server app-v2:8080 weight=5;
}

Monitor error rates, latency percentiles, and business metrics. If anything degrades, roll back automatically.

Feature Flags

Decouple deployment from release:

  • Deploy code to 100% of servers
  • Enable feature for 1% of users
  • Gradually increase to 5%, 25%, 100%
  • Kill switch: disable instantly without redeployment

Observability

You can't test what you can't see. Invest in:

  1. Structured logging (JSON, correlation IDs)
  2. Distributed tracing (OpenTelemetry)
  3. Custom metrics (business KPIs, not just CPU/memory)
  4. Alerting (on symptoms, not causes)

Пријави ме да објавиш коментар

2 коментара

Grace Wilson коментар објављен 5. 4. 2026. 02:22

In hac habitasse platea dictumst. Curabitur aliquam euismod dolor non ornare.

Tom Doe коментар објављен 5. 4. 2026. 02:21

Eposs sunt solems de superbus fortis. Bassus fatalis classiss virtualiter transferre de flavum. Potus sensim ad ferox abnoba. Ubi est audax amicitia. Lorem ipsum dolor sit amet consectetur adipiscing elit. Silva de secundus galatae demitto quadra. Pellentesque vitae velit ex. Teres talis saepe tractare de camerarius flavum sensorem. Aliquam sodales odio id eleifend tristique.