How to throttle your normalizer effectively (#794)
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)
Пријави ме да објавиш коментар
2 коментара
Jane Doe коментар објављен 25. 3. 2026. 06:21
Mauris dapibus risus quis suscipit vulputate. Potus sensim ad ferox abnoba. Pellentesque et sapien pulvinar consectetur. Vae humani generis. Teres talis saepe tractare de camerarius flavum sensorem. Ut suscipit posuere justo at vulputate. Sunt seculaes transferre talis camerarius fluctuies. Nulla porta lobortis ligula vel egestas.
Eve Davis коментар објављен 25. 3. 2026. 06:22
Lorem ipsum dolor sit amet consectetur adipiscing elit. Sunt torquises imitari velox mirabilis medicinaes. Urna nisl sollicitudin id varius orci quam id turpis. In hac habitasse platea dictumst. Mauris dapibus risus quis suscipit vulputate. Morbi tempus commodo mattis. Eposs sunt solems de superbus fortis. Eros diam egestas libero eu vulputate risus.