By value is a concurrency strategy that selects transaction mechanisms according to the business risk of each request.
By value is a concurrency countermeasure for multi-database architectures without distributed transactions. It selects each request’s concurrency mechanism dynamically according to business risk, preventing anomalies or minimizing their business impact. section 9.3.2
Use by value when:
Different requests carry different levels of business risk and therefore should not be forced into one concurrency mechanism. section 9.3.2
A saga must handle isolation anomalies without relying on distributed transactions. section 9.3.2
How Microservices Patterns, Second Edition covers it
How deep it goes
Defines dynamic risk-based selection but does not detail the selection procedure or individual mechanisms.
What it assumes
Assumes familiarity with sagas, multi-database architectures, distributed transactions, and isolation anomalies.
What you can do after
Evaluate/understand how business risk can drive concurrency-mechanism selection.
How it connects
Connects concurrency mechanisms with sagas, distributed transactions, multi-database architectures, and isolation anomalies.
distributed transactionuses · A distributed transaction is a unit of work involving multiple independent resources or systems whose outcome is coordinated as a single transaction.
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.