Decide Where the Interface Needs the Truth

Systems & Architecture · consistency, data integrity, trust

Updated 2026-08-04

Decide, screen by screen, whether the number has to be exact right now or only eventually. Strong consistency and eventual consistency are the two things a system can offer, and the interface is where that choice becomes visible.
Reserve exactness for the decisions that cannot be undone politely:

The last seat, ticket, or unit in stock.
A balance a person is about to spend.
A permission check that grants access.
Anything that charges money.

Let the rest be approximate and fast. A like count, a view count, a notification badge, and a member total can be slightly behind without anyone being harmed.
Never show an exact-looking number for a value that is only eventually correct. 1,247 viewers invites arithmetic that will not hold up, and About 1,200 viewers does not.
Expect the double-booking case to reach the user anyway. Two people can both see the last seat as available, so design the losing screen: what was taken, what is left, and what to do next.
Put the confirmation where the guarantee is, not where the click is. A booking is confirmed when the system has actually reserved it, and an interface that says Confirmed at the moment of the tap is guessing.
Slow the critical path down on purpose when it is the only honest option. A brief wait on a payment is cheaper than a refund and an apology.
Ask the engineers which reads on this screen are guaranteed fresh. The answer is rarely all of them, and knowing which ones changes the copy you write.

Correctness is not a system-wide setting, it is a decision made one screen at a time, and the interface is what tells the user which kind of number they are looking at.