liveBook · Manning

Transaction-per-operation

As explained in Microservices Patterns, Second Edition

Transaction-per-operation is a transaction strategy that executes an entire system operation within one transaction.

Transaction-per-operation implements an entire system operation as a single ACID transaction. It is the simplest and most common transaction strategy in a monolithic architecture. section 6.2.4

Order creation

The createOrder() operation can be implemented as one ACID transaction. A Saga is an alternative that divides the operation into a sequence of ACID transactions across subdomains. section 6.2.4

Figure 6.19 The transaction-per-operation strategy implements a system operation as a single ACID transaction. It’s the simplest and most common approach for implementing transactions in a monolithic architecture.
Transactional Commands transaction per operation

Shows the operation implemented as a single ACID transaction. section 6.2.4

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines the transaction boundary and identifies the strategy as simple and common, without detailing implementation mechanics.
Examples
Uses the createOrder() operation to illustrate transaction strategy choices.
What you can do after
Build a system operation as a single ACID transaction.
How it connects
Connects ACID transactions and monolithic architecture with Saga as an alternative.

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.