Loading content
The transaction concept outlines the process for conducting and managing transactions in information systems. It addresses the requirements for consistency, integrity, and security throughout the entire transaction process.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
A transaction groups related data changes into one unit that either takes effect completely or leaves no effect.
The term comes from processing business and financial operations and was formalized in database systems. ACID properties made atomic, consistent, isolated, and durable processing explicit and testable.
A transaction is like a sealed package: before commit it can be checked and rolled back; afterward other participants see the committed state according to isolation rules. Long packages can still block or compete.
Die Änderung wird vollständig übernommen oder vollständig verworfen.
Parallele Transaktionen beeinflussen sich gemäß einer festgelegten Sichtbarkeitsregel.
Ein bestätigtes Ergebnis bleibt nach einem erfolgreichen Commit erhalten.
Transactions protect balances, orders, and other related state changes from partial processing. They do not automatically solve distributed consistency, incorrect business rules, or arbitrarily long locks.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.