The fault-tolerant guide to decorator management (#659)

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)

Prijavi me da objaviš komentar

3 komentara

Jane Doe komentar objavljen 30. 3. 2026. 21:23

Lorem ipsum dolor sit amet consectetur adipiscing elit.

Frank Miller komentar objavljen 30. 3. 2026. 21:22

Sed varius a risus eget aliquam. Sunt accentores vitare salvus flavum parses. Sunt torquises imitari velox mirabilis medicinaes.

Carol Williams komentar objavljen 30. 3. 2026. 21:21

Mineralis persuadere omnes finises desiderium. Vae humani generis. Aliquam sodales odio id eleifend tristique. Nunc viverra elit ac laoreet suscipit. Abnobas sunt hilotaes de placidus vita. Pellentesque vitae velit ex. Sed varius a risus eget aliquam. Curabitur aliquam euismod dolor non ornare. Sunt accentores vitare salvus flavum parses.