|
| |
Atomicity is the guarantee that a series of operations either succeed or fail together. This is used to avoid partial updates that make no sense from a technical or business perspective. The following are common examples of atomicity.
Databases often have features that allow a series of operations to be committed at once as a single transaction.Business TransactionsA business transaction might involve confirming a shipping address, charging the customer and creating an order. If one of these steps fails, all should fail.File SystemsA file operation such as cut-and-paste whereby the source file isn't deleted unless it is successfully pasted.
HardwareHardware instructions such as test-and-set that involve multiple operations that may be implemented to succeed or fail together.Long Lived TransactionsTransactions that require business logic to implement atomicity because they take too long to use transaction features of databases such as a two-phase commit. For example, a database update that needs to wait for a batch process to run before it can be finalized.
Business processes that involve multiple steps that need to fail or succeed together. For example, a customer account update that can't be finalized until a customer service agent speaks with the customer on the phone.ProceduresProcedures and policies such as the requirement that passengers and their bags always fly on the same aircraft together. |
| Type | | | Definition | The guarantee that a series of operations either succeed or fail together. | | Related Concepts | |
IT Skills
This is the complete list of articles we have written about it skills.
If you enjoyed this page, please consider bookmarking Simplicable.
© 2010-2023 Simplicable. All Rights Reserved. Reproduction of materials found on this site, in any form, without explicit permission is prohibited.
View credits & copyrights or citation information for this page.
|
