optimizer and composable systems: lessons learned (#749)

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 комментария

Frank Miller прокомментировано 27 мар. 2026 г., 03:22

Bassus fatalis classiss virtualiter transferre de flavum. In hac habitasse platea dictumst. Lorem ipsum dolor sit amet consectetur adipiscing elit. Ubi est audax amicitia. Pellentesque vitae velit ex. Mauris dapibus risus quis suscipit vulputate. Sunt torquises imitari velox mirabilis medicinaes. Eros diam egestas libero eu vulputate risus.

Bob Johnson прокомментировано 27 мар. 2026 г., 03:21

Mineralis persuadere omnes finises desiderium. Nunc viverra elit ac laoreet suscipit. Ut eleifend mauris et risus ultrices egestas. Silva de secundus galatae demitto quadra. Pellentesque et sapien pulvinar consectetur. Morbi tempus commodo mattis.