liveBook · Manning

Nonrepeatable read

As explained in Microservices Patterns, Second Edition

A fuzzy read is a concurrency anomaly in which repeated reads of the same data return different values because another transaction modifies it between reads.

A nonrepeatable read, also called a fuzzy read, occurs when two steps of a saga read the same data and receive different committed values because another transaction or saga updated it between reads. section 9.3.1

Sagas lack isolation across services, so concurrent execution can produce this anomaly even when each service prevents local anomalies. Application-level countermeasures address saga data anomalies, though no specific countermeasure is assigned here to nonrepeatable reads. section 9.3.1 section 9.4

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines the changed-value condition but does not trace a dedicated instance or prescribe a specific remedy.
What you can do after
Understand how concurrent saga steps can read different committed values after an intervening update.
How it connects
Connects nonrepeatable reads to sagas, transactions, isolation, and serialization anomalies.

Also explained in

Compare how 2 books explain nonrepeatable read →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.