- Difficulty
- Intermediate
- Time
- 45–60 min
Hold the schedule
Sketch the durable state of a scheduled post from author submission to publication, and name the record that lets a schedule survive a process restart. State what the author sees between submission and the publish time.
What to demonstrate: Is the schedule a durable object rather than a timer in memory?
Edit and cancel
An author edits one post and cancels another, both seconds before their publish time. Define the allowed transitions, and say what happens to an edit or cancellation that arrives while publication is already in flight.
What to demonstrate: Do you reason about the race rather than the happy path?
Publish once
Make publication idempotent across retries and duplicate workers, and explain how that guarantee interacts with fanout to followers. Say what a retry after an ambiguous timeout must do.
What to demonstrate: Can you bound duplicate side effects without dropping the post?
Operate it
Add local-time scheduling, a limit on how much an account can queue, and the telemetry that shows scheduling falling behind. Name the one signal you would wake someone for.
What to demonstrate: Does the operational story match the failure the product would actually hit?