One caution on the session-based pin: keep it narrow. Pinning every read for a few seconds after any write sends the whole dashboard to the primary, including the heavy catalog queries the replicas exist to serve. I pin only the read-your-writes route itself, My Orders in this case, and leave everything else on the replica. Lag protection only earns its cost where a stale row actually breaks the flow.