Replication lag is the time between a write on a primary database node and the change appearing across its replicas. During that delay, different readers may see different versions of the data. section 8.2.2
A profile picture catching up
After a profile picture changes, Server A may show the new image while Server B still serves the old one. Once synchronization catches up, both replicas reflect the change. section 8.2.2
An order that appears missing
After a customer places an order, the event consumer may not have updated the database when the orders page loads. Showing a “Processing...” card can reassure the customer instead of displaying an empty list. section 7.3.3
Figure 7.7 Client-Side Intelligence (Optimistic UI) at work. We show the user the success state before the server has actually finished the work.

Shows an optimistic interface displaying the expected result before the server finishes processing. section 7.3.3





