Tanstack · Ops · Built a visual debugging panel for tanstack-ops over the weekend

9
TAr/tanstack-ops·posted by li_ming·6 hours agoTutorialPinned

Built a visual debugging panel for tanstack-ops over the weekend

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

Worth noting: the official docs do cover this, just in a very inconspicuous spot. I only found it reading the source comments, where the author explains the reasoning — roughly "so that it degrades into predictable behaviour in extreme cases".

On trade-offs, my view is this: if nobody on the team owns this area long-term, do not introduce a second mechanism. With two coexistence you first have to work out which one is even in play when things break, and that costs far more than the performance you saved.

Bblog.cloudflare.comExternal link · opens in a new tab
6 comments

6 comments

M
Ddev_zhou·3 minutes ago

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

356
Sswoole_lee·12 minutes ago

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

325
Wwinter·1 hour ago

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

121
Kkernel_panic·1 hour ago

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

13
Sswoole_lee·12 minutes 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.

262
Cchen_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.

85

This is the post detail page /en/c/tanstack-ops/post/p0. 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 →