China Developer Brief: A QPS Target Needs a Correctness Test
One source-checked engineering discussion: how to distinguish a short-link throughput target from measured, correct redirects. Read the full companion briefing in Guides for the measurement table and architecture review questions.
Source-reviewed edition · revision 1 · saved Oct 19, 2026, 2:33 PM CST
The briefing is our selected English reading guide. The daily archive preserves the broader ranking record and saved notes.
Can a Short-Link Service Really Reach 100,000 QPS in One Weekend by Just Adding Redis?
The reader’s brief
Before sharing a large QPS number, ask what passed: status, destination, latency and workload. Preserve the test window, hot/cold key distribution, dropped iterations and error counts. This article is useful as a measurement checklist, with an explicit unmeasured target. For our full review, open the dated developer briefing from Guides.
Bug Jun's October 16 Juejin article presents 100,000 QPS as a target, not a measured achievement. The author says k6 was unavailable in the validation environment. Its lab starts with one Go process, in-memory mappings and a local append log; PostgreSQL and Redis are a proposed later evolution. A correct redirect requires 302 and the matching Location header. Disable automatic redirect following for endpoint-only tests, and separate planned arrivals, requests sent and correct responses. Grafana's constant-arrival-rate executor starts iterations independently of response time while virtual users are available; its configured rate alone is not achieved correct-response throughput. We read both sources; we did not execute the code, reproduce throughput or audit the implementation.
Context: The source article is dated October 16. ThreadEast first observed it October 18 at 00:58 CST and observed it again October 19 at 13:05 CST (UTC+8), Juejin number 2. Observation and ranking do not establish adoption or performance.
Observation record
Recorded at #2 on Juejin via UAPI, Oct 19, 2026, 1:05 PM CST. This rank describes that source’s listing.
Edition history & corrections (1)
Historical editions preserve the wording available at the time. Share the current briefing URL.
- Revision 1 · Oct 19, 2026, 2:33 PM CST