Tanstack · Ops · Choosing tanstack-ops: I turned 5 options into a side-by-side comparison

2
TAr/tanstack-ops·posted by zhu_zong·3 days agoJobs

Choosing tanstack-ops: I turned 5 options into a side-by-side comparison

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

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.

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".

Pphp.netExternal link · opens in a new tab
0 comments

0 comments

M

No comments yet. Whoever speaks first tends to set the tone for the whole thread.

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