Write skew
Write skew is a concurrency anomaly in which individually valid, concurrent updates based on overlapping observations jointly violate a consistency constraint.
Clojure: The Essential Reference
Write skew is a concurrency anomaly in which transactions independently update different shared references while jointly violating a constraint.
- How it is used
- Uses STM transactions to reason about constraints spanning multiple refs during concurrent updates.
- How deep it goes
- Defines the anomaly and works through a Clojure voting example, but does not develop a broader taxonomy of isolation anomalies.
- Examples
- Demonstrates concurrent voting batches sharing a honeypot threshold across separate refs.
- What you can do after
- Diagnose shared-ref consistency risks and apply ensure when transaction validity depends on another ref.
Read how Clojure: The Essential Reference explains write skew →
Microservices Patterns, Second Edition
A concurrency anomaly in which concurrent operations read overlapping data and update disjoint data in a way that violates an invariant.
- How it is used
- Identifies invariant-breaking outcomes caused by concurrent sagas in a microservice architecture.
- How deep it goes
- Defines the anomaly and situates it among saga interleavings, without detailing a prevention strategy.
- Examples
- Uses concurrent create-order and cancel-order sagas that affect customer credit.
- What you can do after
- Understand how concurrent sagas can violate business invariants despite locally correct transactions.
Read how Microservices Patterns, Second Edition explains write skew →
Also covered in
- The Coder CafeIn early access (MEAP)
- Latency
What to know first
- consistencyConsistency is the degree to which related data, behavior, or results agree with one another and conform to applicable rules or expectations.
- snapshot isolationSnapshot isolation is a transaction-isolation method in which each transaction reads a consistent versioned snapshot of committed data while concurrent writes are isolated from that view.
- database transactionA database transaction is a bounded unit of database operations whose changes are treated as one logical whole, typically committed or rolled back together.
Related concepts
- serialization anomalykind of · A serialization anomaly is an outcome of concurrent operations that cannot be explained by any serial execution order.
- database transactionuses · A database transaction is a bounded unit of database operations whose changes are treated as one logical whole, typically committed or rolled back together.
- snapshot isolationproduced by · Snapshot isolation is a transaction-isolation method in which each transaction reads a consistent versioned snapshot of committed data while concurrent writes are isolated from that view.
- consistencycontrasts with · Consistency is the degree to which related data, behavior, or results agree with one another and conform to applicable rules or expectations.
- read skewcontrasts with · Read skew is a concurrency anomaly in which a transaction observes individually valid values that together represent no consistent overall state.
Questions about write skew
What is write skew?
Write skew is a concurrency anomaly in which individually valid, concurrent updates based on overlapping observations jointly violate a consistency constraint.
Which Manning books explain write skew?
Clojure: The Essential Reference and Microservices Patterns, Second Edition.
What should I know before learning write skew?
Manning books that teach write skew usually introduce consistency, snapshot isolation and database transaction first.
What is the difference between write skew and consistency?
Write skew is a concurrency anomaly in which individually valid, concurrent updates based on overlapping observations jointly violate a consistency constraint. Consistency is the degree to which related data, behavior, or results agree with one another and conform to applicable rules or expectations.
What is write skew a kind of?
Write skew is a kind of serialization anomaly. A serialization anomaly is an outcome of concurrent operations that cannot be explained by any serial execution order.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

