Transaction boundary
A transaction boundary defines the scope of operations treated as a single transaction and governed together by its outcome and consistency rules.
Microservices Patterns, Second Edition
A transaction boundary defines the scope within which operations are governed by rules for success, failure, concurrency, conflicts, and visibility.
- How it is used
- Frames transaction boundaries as correctness scopes for system operations, especially when operations span services.
- How deep it goes
- Defines commit and abort behavior, invariants, conflicts, isolation, and visibility, then relates local transactions to cross-service operations.
- Examples
- Uses a product lookup, conditional customer-credit update, and order insertion as one SQL transaction.
- What you can do after
- Understand why cross-service commands and queries cannot rely on one ACID transaction.
Read how Microservices Patterns, Second Edition explains transaction boundary →
Clean Applications with Hexagonal Architecture
A transaction boundary defines the scope within which a set of operations participates in one atomic transaction.
- How it is used
- Defines the handler as the atomic unit of work for a hexagonal use case.
- How deep it goes
- Explains placement, runtime interception, event timing, and focused transaction testing.
- Examples
- Uses an article publish handler and a read-only article query handler to illustrate transaction declarations.
- What you can do after
- Operate/configure handler-level transactions and verify their outcomes with focused Spring integration tests.
Read how Clean Applications with Hexagonal Architecture explains transaction boundary →
Also covered in
What to know first
- asynchronous communicationAsynchronous communication is the exchange of information without requiring participants to interact at the same time or the sender to wait for the receiver to process a message.
Related concepts
- batchingused by · Batching is the grouping of multiple items, requests, or operations so they can be processed together as a unit.
- handlerpart of · A software component that responds to an input by performing the processing or platform-specific actions associated with it.
- Transactional annotationused by · Spring’s @Transactional annotation declares that a method or class should participate in managed transaction execution.
- database transactionpart of · A database transaction is a bounded unit of database operations whose changes are treated as one logical whole, typically committed or rolled back together.
Questions about transaction boundary
What is transaction boundary?
A transaction boundary defines the scope of operations treated as a single transaction and governed together by its outcome and consistency rules.
Which Manning books explain transaction boundary?
Microservices Patterns, Second Edition and Clean Applications with Hexagonal Architecture.
What should I know before learning transaction boundary?
Manning books that teach transaction boundary usually introduce asynchronous communication first.
What is transaction boundary part of?
Transaction boundary is part of handler. A software component that responds to an input by performing the processing or platform-specific actions associated with it.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

