ORCIDGitHubLinkedIn
RSS Curriculum Vitae TR

Transaction

Turkish equivalent: İşlemDomain: Databases

A logical unit of database work whose operations are committed together or rolled back together when the unit cannot complete.

A transaction groups one or more reads and writes inside a single consistency boundary. The engineering question is broader than issuing COMMIT: where the transaction begins, which data version it observes, which locks or MVCC versions it depends on, and what is rolled back after failure all belong to the same unit.

When the Boundary Is Wrong

An excessively broad transaction increases lock duration, undo/redo volume, and contention. A boundary that is too narrow splits one business invariant across independent commits and turns partial success into an application-level failure mode. Transaction scope should therefore follow the invariant being protected rather than an arbitrary service or repository boundary.

Related: Database Management Systems, Oracle Database and PL/SQL.

Updated:

Related concepts

Databases

Related technical publications

Publications whose title or summary directly references this concept.

Database Management Systems

Database course notes covering ER modeling, the relational model, normalization, SQL querying, transaction management, database objects, indexing and access control.

Safe Row Updates in Oracle Without Reliable Unique Keys

Why a single-row update is unsafe in legacy Oracle tables whose uniqueness the database never enforced: separating business key from physical row identity, deterministic candidate selection, ROWID targeting, transaction boundaries, and ORM identity assumptions.

Dynamic Data Source Routing with HikariCP

AbstractRoutingDataSource does not create a pool; it routes a connection request to one of the independent HikariCP pools according to the key selected before the transaction starts.

Building a Reflection-Based ORM in Java

In a lightweight reflection-based ORM, the important costs come from metadata mapping, type conversion, transaction boundaries, and reuse of reflection metadata rather than SQL string generation alone.