OLTP

OLTP, or Online Transaction Processing, describes database systems built to handle many small, fast transactions from many concurrent users. OLTP systems are the operational backbone of applications: order entry, banking, ticketing, inventory, and user account management.

How It Works

OLTP workloads consist of short read and write operations that touch few rows — placing an order, updating a profile, recording a payment. The defining characteristics are:

• High concurrency: thousands of simultaneous transactions.
• Low latency: each operation completes in milliseconds.
• ACID guarantees: transactions are reliable and isolated.
• Normalized schemas: data is structured to minimize redundancy and protect integrity.
• Row-oriented storage: efficient for reading and writing whole records.

Relational databases such as PostgreSQL, MySQL, Oracle, and SQL Server are the classic OLTP engines, though many NoSQL stores also serve OLTP-style workloads.

Why It Matters

OLTP systems run the live operations of a business. Their correctness and responsiveness directly affect users completing purchases or transfers. The emphasis is on transactional integrity and concurrency, not on scanning huge volumes of historical data.

That focus is also their limitation: OLTP databases handle analytical queries over large datasets poorly. Heavy reporting on an OLTP system can slow live operations, which is why analytics is usually offloaded to OLAP systems and data warehouses via ETL or change data capture.

Related Terms

OLTP is the operational counterpart to OLAP, depends on ACID transactions and normalization, and typically feeds a data warehouse.