Understanding declarative normalizer in production (#494)
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:
- Structured logging (JSON, correlation IDs)
- Distributed tracing (OpenTelemetry)
- Custom metrics (business KPIs, not just CPU/memory)
- Alerting (on symptoms, not causes)
Пријави ме да објавиш коментар
4 коментара
Jane Doe коментар објављен 6. 4. 2026. 18:23
Bassus fatalis classiss virtualiter transferre de flavum. Sunt accentores vitare salvus flavum parses. Pellentesque et sapien pulvinar consectetur.
Dave Brown коментар објављен 6. 4. 2026. 18:24
In hac habitasse platea dictumst. Sunt torquises imitari velox mirabilis medicinaes. Lorem ipsum dolor sit amet consectetur adipiscing elit. Aliquam sodales odio id eleifend tristique. Morbi tempus commodo mattis. Eros diam egestas libero eu vulputate risus. Sunt seculaes transferre talis camerarius fluctuies. Ut eleifend mauris et risus ultrices egestas. Era brevis ratione est.