liveBook · Manning

Reread value

As explained in Microservices Patterns, Second Edition

Reread value is a concurrency technique that rereads a record before overwriting it and aborts when the record has changed since its earlier read.

Reread value is an application-level concurrency technique for sagas. Before overwriting a record, a transaction rereads it and aborts if the value changed since the earlier read. section 9.3.2

The technique addresses missing isolation in multi-database sagas by preventing dirty writes. It belongs with other application-level countermeasures for anomalies such as lost updates, dirty reads, and fuzzy reads. section 9.3.2 section 9.4

Use reread value when an update must verify that its earlier view remains valid:

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines the reread-and-abort rule and its anomaly target, but does not detail implementation mechanics or selection criteria.
What it assumes
Assumes familiarity with sagas, multi-database transactions, missing isolation, and dirty writes.
What you can do after
Apply reread value in a saga to detect changed records and avoid overwriting newer data.
How it connects
Connects sagas, transaction isolation, dirty writes, data anomalies, and application-level concurrency countermeasures.

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.