Realtime with Optimistic Updates Volume 07 - Advanced Application Architecture
The same mutation can generate two signals User A clicks DONE -> optimistic UI predicts DONE -> HTTP PATCH /tasks/:id -> Postgres commits DONE -> Broadcast event arrives -> mutation response arrives -> onSettled invalidates too
Is duplicate invalidation wrong? Usually no. Invalidation is idempotent from the application point of view: both signals say “the cache may be stale.” The cost is extra refetch work, not data corruption. Optimize only if measurements show meaningful churn.
Do not suppress every self-originated event Trying to perfectly identify “my own” database broadcast adds correlation state and can accidentally ignore a server-side change you still need. TaskFlow first accepts harmless duplicate freshness signals.
Conflict behavior • If another user changes the Task while your optimistic mutation is pending, the server remains the authority.
• Serial mutation scopes from Phase 25 still protect same-Task mutation order in the local client.
• Realtime invalidation helps surface remote commits quickly.
• A 409/403 response still rolls back the local optimistic prediction.
Rule Optimistic UI improves perceived latency. Realtime improves cross-client freshness. Neither becomes the source of truth.
Realtime with Optimistic Updates matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.
Restate the goal of “Realtime with Optimistic Updates” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: user action → snapshot → optimistic cache → server result → commit/rollback. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Realtime task updates that merge into TanStack Query state with scoped subscriptions and reconnect behavior.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
onMutate: async (input) => {
await queryClient.cancelQueries({ queryKey: taskKeys.all });
const previous = queryClient.getQueryData(taskKeys.all);
applyOptimisticChange(input);
return { previous };
},
onError: (_err, _input, ctx) => restore(ctx?.previous),Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “Realtime with Optimistic Updates” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Create a channel scoped to workspace/board context and define subscription lifecycle.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Duplicate optimistic + realtime updates
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.