Realtime Mental Model and When It Earns Its Place Volume 07 - Advanced Application Architecture
The problem Realtime solves • User A changes a Task while User B is looking at the same Workspace.
• Without Realtime, User B sees the change only after manual refresh, navigation, focus refetch, or polling.
• Realtime reduces the time between committed server truth and another client learning that it changed.
Do not confuse freshness with authority The event does not become the database. The browser uses the event as a hint that cached server state may now be stale. HTTP/API reads still reconstruct authoritative state.
When Realtime earns its cost • Collaborative task boards where changes from coworkers should appear quickly.
• Live operations consoles where stale state has real workflow cost.
• Notifications or activity streams where delay matters.
• Presence/typing/cursor indicators for collaborative experiences.
When normal refetch is enough • Rarely changed settings pages.
• Forms mostly edited by one person.
• Admin reports where refresh every 30-60 seconds is acceptable.
• Screens where realtime complexity would exceed UX value.
Decision rule Start with HTTP + TanStack Query. Add Realtime only to flows where stale data is an actual product problem.
Realtime Mental Model and When It Earns Its Place 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 Mental Model and When It Earns Its Place” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: database change → event stream → subscription → cache reconciliation → UI. 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.
channel.on("postgres_changes", filter, payload => {
queryClient.invalidateQueries({ queryKey: taskKeys.all });
});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 Mental Model and When It Earns Its Place” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Choose the exact collaborative event that benefits from realtime rather than subscribing to everything.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Realtime treated as database authority
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.