Course contentsShow
← Java
Lesson 2052 of 2,87041. NIO.2 and the Path APIFree lesson

Atomic Writes and File Creation Guarantees

Understand the atomicity guarantees of Files.write operations and when file creation is guaranteed.

Atomic Writes and File Creation Guarantees

What you'll learn: How Files.write operations ensure file creation is complete and visible as a single unit, preventing partial writes or corrupted intermediate states.

What Does Atomic Mean?

When a write operation is atomic, it either completes entirely or doesn't happen at all—there's no in-between state visible to other processes. Think of it like dropping a letter in a mailbox: the letter is either fully in the box or still in your hand; nobody sees it halfway through the slot.

Files.write Atomicity

When you use Files.write() with certain OpenOptions, Java provides atomicity guarantees:

Path file = Paths.get("config.txt");
String content = "key=value";

// Atomic write with CREATE and TRUNCATE_EXISTING
Files.writeString(file, content, StandardOpenOption.CREATE, 
                  StandardOpenOption.TRUNCATE_EXISTING);

By default, Files.write operations are atomic for file creation. If the file doesn't exist, it will be fully created with its content before any other process can observe it. You won't have a situation where another thread reads a half-written file during creation.

The ATOMIC_MOVE Guarantee

For even stronger atomicity, use StandardOpenOption.ATOMIC_MOVE when applicable (typically with move operations). This ensures the file appears atomically at its final location.

When Atomicity Matters

This guarantee is crucial for:

  • Configuration files that other processes read
  • Data integrity where partial writes would cause corruption
  • Concurrent applications where multiple threads access the same file

Without atomicity, a crash mid-write could leave corrupted data or a half-written file that breaks your application's assumptions.

Key Takeaway: Files.write operations provide atomic file creation guarantees, ensuring the file appears complete and consistent to all observers—no partial or intermediate states are visible during the write process.