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.

Developing a NiFi Custom Processor with Java

Java custom processor development in Apache NiFi: Processor API, FlowFiles, ProcessSessions, lifecycle, transaction integrity, provenance, backpressure, clustering, concurrency, and verification.

Database Management Systems

Database-systems course notes covering ER and relational models, normalization, relational algebra, SQL, transactions and access control together with storage engines, buffer pools, B+ trees, WAL, and crash recovery.

Spring Boot

Advanced Spring Boot notes for the Spring Boot 4 and Spring Framework 7 generation, covering auto-configuration, dependency injection, MVC/REST, Jakarta Persistence, transactions, security, testing, HTTP clients, virtual threads, observability, Native Image, and production reliability.