N8Timeouts and deadline propagation

The problem

1 s on screen = 100 ms

Why does a server keep working for a user who already closed the tab?

A clock per hop

Users give up after 0.6 s. The API also waits up to 0.6 s, counted from when it calls the database.

Live metrics for each version of the scene
Metric	Own clocks	One clock	Change
	—	—	—
target ≤ 400 ms	—	—	—
	—	—	—
	—	—	—

N8Timeouts and deadline propagation

A request crossing three services needs one deadline, not three, or the back end keeps working for a client that has already left.