接口与协议
rate-limiting-logging
更新于 2026-09-30
Rate Limiting · 日志规则
Logging rules for Rate Limiting: structured fields, correlation ids and single-boundary failure logging.
- 技术栈
- Rate Limiting
- 主题
- 日志
- 条目
- 9 条
- 版本
- v0.2.0
✓ 应当这么做
- ✓ Log structured key/value pairs, not interpolated prose
- ✓ Attach a correlation id shared by every hop of one request
- ✓ Log once at the failure boundary, not at every layer it passed through
✕ 常见反模式
- ✕ Logging full payloads that may contain personal data
- ✕ Debug-level spam left enabled in production configuration
- ✕ Log statements as the only signal for a metric-worthy event
◎ 交付前验证
- ◎ Integration tests cover the success and the failure branch of each new route
- ◎ No unhandled promise rejection warnings in the test output
- ◎ Graceful shutdown drains in-flight requests
同分类条目
13 篇接口与协议
REST API 工程规则
REST design rules: resource naming, idempotent verbs and typed error envelopes
接口与协议
OpenAPI Contract 工程规则
OpenAPI rules: spec-first changes and generated client parity in CI
接口与协议
WebSocket 工程规则
WebSocket rules: authenticated handshake, heartbeat and backpressure
接口与协议
SSE Streaming 工程规则
SSE rules: bounded event size, heartbeat comments and reconnect semantics
接口与协议
Rate Limiting 工程规则
Rate limit rules: per-principal quotas and explicit 429 semantics