Code on a screen, representing an atomic operation.

An action that happens completely or not at all.

What an atomic operation is

An atomic operation is one that completes as a single, indivisible step: it either happens entirely or not at all, with no partially completed state visible to the rest of the system. The term comes from the idea of something that cannot be divided. To other parts of a program, an atomic operation appears to occur instantaneously, so they never catch it halfway through.

Indivisible by design

The defining quality of an atomic operation is indivisibility. While the operation may internally involve several steps, it is treated as one unit that cannot be interrupted partway in a way that exposes an intermediate state. This means no other task can observe the operation as half-done; it sees either the state before the operation or the state after, but never in between.

Why atomicity matters in concurrency

Atomic operations are especially important when multiple tasks run at the same time and share data. If an operation were not atomic, another task might observe or interfere with it midway, leading to incorrect results. By guaranteeing that the operation happens as an indivisible whole, atomicity prevents such interference, helping keep shared data consistent when many tasks operate concurrently.

Avoiding partial updates

A key benefit of atomic operations is that they avoid partial updates being seen. When data is changed atomically, there is no moment where the change is only half-applied from another task's perspective. This protects against a class of subtle bugs that can occur when concurrent tasks glimpse incomplete changes, making programs more predictable and correct.

Where atomic operations are used

Atomic operations appear throughout computing wherever correctness under concurrency matters, from low-level programming to databases, where transactions are expected to be atomic. They are a building block for safely coordinating shared data among concurrent tasks. Understanding atomicity helps explain how systems maintain consistency when many things happen at once.

Why it matters

Atomic operations are a fundamental concept for correct concurrent and reliable systems. Understanding what an atomic operation is - an action that happens completely or not at all - clarifies how shared data stays consistent when tasks run together. For anyone interested in concurrency, it is a valuable concept to understand.

See also: What is a race condition? Explained, What is a mutex? Explained.

Sources

Published date reflects the original event date (2026-01-27). This article is original Skillo editorial written from the sources above; facts were verified in September 2026.

Skillo Staff

Skillo Staff

All stories by: Skillo Staff

Leave a Reply