Loadingone moment…
A social app publishes follow and unfollow events. The producer retries whenever it is not certain a message got through, so the same event routinely arrives more than once — sometimes in the same batch, sometimes an hour later. Follower counts are computed from these events and shown in the app, and they are drifting upward.
The cadence — and what it does to the duplicate problem.
Practice studio
Run the review to check your architecture against this scenario — a valid DAG, a trigger for the freshness SLA, a transform stage, a quality gate before publish, and a failure path — then defend it in a short interview.
This scenario runs a full workspace — editor, canvas and results side by side. It needs a laptop or desktop to be usable. Open this page on a bigger screen to start building.