# Read From Primary After Write

> A technique for routing a client's reads to the primary for a short time after it writes, so it sees its own write.

Record: `lexicon:read-from-primary-after-write`
Kind: technique
Layer: [Atomic Boundary](https://banes-lab.com/records/layer/atomic-boundary.md)
Canonical: https://banes-lab.com/ontology/lexicon#lexicon-read-from-primary-after-write

Listed in [Lexicon terms](https://banes-lab.com/api/records/lexicon.md), after [Make Immutable](https://banes-lab.com/records/lexicon/make-immutable.md) and before [Consistency Contract](https://banes-lab.com/records/lexicon/consistency-contract.md).

## Category

- [Transactions / State / Concurrency](https://banes-lab.com/records/lexicon-category/transactions-state-concurrency.md)

## Refactors

- [Read-Your-Writes Violation](https://banes-lab.com/records/architecture/read-your-writes-violation.md)
- [Causal Consistency](https://banes-lab.com/records/architecture/causal-consistency.md)

## Linked from

- [Anti-patterns](https://banes-lab.com/ontology/principles/architecture-category-anti-patterns.md)
- [Causality / Ordering / Distributed Time](https://banes-lab.com/ontology/principles/architecture-category-causality-ordering-distributed-time.md)
