CTCLI Tools · Career
Community homeHot discussions Latest posts Best of Knowledge base Resources About

CLI Tools · Career · Building an internal platform with cli-tools-career from scratch: architecture and decision log

121
CTr/cli-tools-career·posted by huang_ke·1 hour agoTooling

Building an internal platform with cli-tools-career from scratch: architecture and decision log

Some background first. Our setup is cli-tools-career plus three downstream services, seven figures of daily requests, peaking around nine in the evening.

We also fixed monitoring along the way: replaced average-based alerts with percentiles and split them per endpoint. False alerts dropped by about seventy percent and the on-call rotation visibly cheered up.

Performance44%
Maintainability28%
Ecosystem and community17%
Hiring difficulty11%

206 votes total

15 comments

15 comments

M
Kkernel_panic·1 hour ago

I just read the cli-tools-career source — the author actually explains the reasoning in a comment, roughly "so that it degrades into predictable behaviour in extreme cases".

437
Kkernel_panic·12 minutes ago

Sharing our numbers, 8 cores 16GB, same scenario:

| Concurrency | P50 | P99 |
|---|---|---|
| 200 | 12ms | 88ms |
| 500 | 31ms | 340ms |

P99 clearly collapses at 500 concurrency, which lines up with your knee point.

150
Rran_bo·5 hours ago

We have run this in production for two years without hitting it. That said, we never reached this scale, so our experience is not really evidence here.

82
Aalice_dev·3 minutes ago

Agreeing with the above. One addition: with this option enabled the GC count in your metrics doubles, so adjust the alert threshold at the same time or it will keep firing.

423
Wwinter·2 days ago

Can you give a minimal reproduction? I ran it locally for ten minutes and could not reproduce on macOS with the latest version.

37
Cchen_dev·1 hour agoedited

Saved. I am reworking this area this week — this saves a lot of wrong turns.

273
Mmike_xu·28 minutes agoedited

Worth learning from this debugging approach. We went straight at the logs and took a much longer route.

67
Nnikic·3 minutes ago

There is actually a simpler fix that needs no architecture change: move this check up to the gateway and the problem disappears. The cost is one extra lookup at the gateway.

102
Zzhu_zong·28 minutes ago

I just read the cli-tools-career source — the author actually explains the reasoning in a comment, roughly "so that it degrades into predictable behaviour in extreme cases".

23
Ddev_zhou·28 minutes ago

This matches what we see in production. We only hit it past 3k QPS; the earlier load tests showed nothing — the test traffic was too clean, with no long-tail requests.

2
Ddev_zhou·just now

This is not a cli-tools-career problem, it is a usage problem. The docs say this API is not thread-safe and you must lock around it yourself.

402
Aalice_dev·1 hour ago

I see point 3 differently. The trade-off depends on your read/write ratio: read-heavy with little writing means caching actually widens the inconsistency window.

8
LlinlinOP·yesterday

One counter-example: below cli-tools-career 7.4 the semantics of that code are different, so do not copy it verbatim. We got burned in staging and rolled back once.

93
Ttang_haoOP·1 hour ago

Thanks for sharing real numbers — far more useful than the articles that only cover concepts.

14
Rrase·just nowedited

Has anyone run a controlled experiment? I did, reducing it to a single variable, and the difference was 4% — within noise. So I suspect the main cause is something else.

38

This is the post detail page /en/c/cli-tools-career/post/p5. Posts and comments are generated deterministically from a seeded PRNG, so the same post always renders the same content and the link can be shared, reloaded and indexed. In production this page reads MySQL for the post, Redis for hot-post caching, and fetches the whole comment tree in a single query on the path column.

See the database schema →