Discussion: is the baking-events ecosystem being replaced by another stack?

BAr/baking-events·posted by nikic·yesterdayOpen source

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

The first thing was to collapse the variables. We were changing config and upgrading the version at the same time, and afterwards nobody could say which change caused what. We rolled back to moving one variable at a time, re-ran three times, and only then did the curve settle. Tedious, but not skippable.

Image placeholder · object storage in production
POST /api/uploads → CDN origin pull

2 commentsWith image

2 comments

Bbob_chen·3 minutes ago

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.

Oops_wang·28 minutes ago

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

This is the post detail page /en/c/baking-events/post/p3. 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 →

Baking · Events · Discussion: is the baking-events ecosystem being replaced by another stack?

Discussion: is the baking-events ecosystem being replaced by another stack?

2 comments