liveBook · Manning

Pending state

As explained in Microservices Patterns, Second Edition

A pending state is a business-entity state indicating that an operation is in progress and its result is not yet committed.

A pending state marks a business entity as being updated by a saga, with the result not yet committed. Setting the state signals other transactions to act accordingly; this application-level flag is a semantic lock. section 9.3.2

Order update

A saga such as the Create Order Saga can begin by setting an Order to APPROVAL_PENDING before updating it. section 9.3.2

How Microservices Patterns, Second Edition covers it

How deep it goes
Explains the state’s role as a semantic lock and its use at the start of saga updates.
Examples
Uses an Order in APPROVAL_PENDING and the Create Order Saga as an example.
What it assumes
Assumes familiarity with sagas and their lack of transaction isolation.
What you can do after
Apply semantic-lock flags to signal that saga-updated records are not yet committed.
How it connects
Connects pending states to sagas, semantic locks, and transaction-isolation anomalies.

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.