Transaction processing

information assets characterized by such a high volume, velocity, and variety to require specific technology and analytical methods for its transformation into value

2013–2018 British political consulting firm

In computer science, ACID (atomicity, consistency, isolation, durability) is a set of properties of database transactions intended to guarantee data validity despite errors, power failures, and other mishaps. For example, a transfer of funds from one bank account to another, involving multiple changes such as debiting one account and crediting another, is a single transaction.

unit of work performed within a database management system

maintenance of, and the assurance of the accuracy and consistency of, data over its entire life-cycle

without repeating data entry for a financial transaction

information processing that is divided into individual, indivisible operations

information system facilitating and managing transaction-oriented applications

type of computing system

operation which returns the database to some previous state, which is crucial for recovering from database server crashes

concurrency control method commonly used by database management systems

IBM CICS (Customer Information Control System) is a family of mixed-language application servers that provide online transaction management and connectivity for applications on IBM mainframe systems under z/OS and z/VSE.

database that stores data relating to time instances

measures to ensure concurrent computing operations generate correct results

type of atomic commitment protocol

abstract model to describe execution of transactions running in the system

property of a database system that determines how transaction integrity is visible to other users and systems

record of changes made to stored data by a database management system or filesystem, which can be rolled back to implement transactional guarantees

American computer hardware manufacturer ( 1974–1997)

distributed transaction processing standard

property of a database system ensuring that a transaction can only bring the database from one valid state to another, maintaining database invariants (constraints, cascades, triggers etc.)

that a transaction is either completed completely or not at all

concurrency control mechanism, analogous to database transactions for controlling access to shared memory in concurrent computing, that simplifies concurrent programming by allowing a group of load and store instructions to execute in an atomic way

concurrency control locking protocol in databases and transaction processing

software

Concurrency control method

concurrency control mechanism for controlling access to shared memory in concurrent computing

IBM mainframe operating system used for transaction processing

thumb|In grey a linear sub-history, processes beginning in do not have a linearizable history because or may complete in either order before occurs.

A savepoint is a way of implementing subtransactions (also known as nested transactions) within a relational database management system by indicating a point within a transaction that can be "rolled back to" without affecting any work done in the transaction before the savepoint was created. Multiple savepoints can exist within a single transaction. Savepoints are useful for implementing complex error recovery in database applications. If an error occurs in the midst of a multiple-statement transaction, the application may be able to recover from the error (by rolling back to a savepoint) with

a set of formally specified rules that guarantee (or explicitly disclaim) certain consistencies in the event of concurrent reads or writes to shared memory

database transaction between two or more networks

usually in database management

component of Windows Vista and later operating systems

Software

property of a database system guaranteeing that transactions that have committed will survive permanently in the event of crashes

minimum number of votes that a distributed transaction has to obtain in order to be allowed to perform an operation in a distributed system

component of Microsoft Windows

computer operation that makes a set of tentative changes permanent

FoundationDB is a free and open-source multi-model distributed NoSQL database owned by Apple Inc. with a shared-nothing architecture. The product was designed around a "core" database, with additional features supplied in "layers." The core database exposes an ordered key–value store with transactions. The transactions are able to read or write multiple keys stored on any machine in the cluster while fully supporting ACID properties. Transactions are used to implement a variety of data models via layers.

database management system designed to support multiple data models against a single, integrated backend