File API

🔍 What Is It?

Modern API (use this):

• →java.nio.file.Path — represents a file or directory path (replaces java.io.File)
• →java.nio.file.Files — utility class with all file operations
• →java.nio.file.Paths — factory for Path objects (Java 7-10)
• →Path.of() — factory for Path objects (Java 11+, preferred)

Legacy API (avoid in new code):

• →java.io.File — old path representation
• →java.io.FileInputStream/FileOutputStream — byte streams
• →java.io.FileReader/FileWriter — character streams (no charset control!)
• →java.io.BufferedReader/BufferedWriter — buffered wrappers

Key Files methods:

• →readString(path) / readAllBytes(path) / readAllLines(path) — read entire file
• →writeString(path, content) / write(path, bytes) — write entire file
• →lines(path) — Stream<String> of lines (lazy)
• →copy(source, target) / move(source, target) / delete(path)
• →createFile(path) / createDirectory(path) / createDirectories(path)
• →exists(path) / isDirectory(path) / isRegularFile(path)
• →walk(path) — Stream<Path> of all files recursively
• →list(path) — Stream<Path> of immediate children

🎯 Why Do We Need It?

The legacy java.io.File API has many problems:

• →Methods return false instead of throwing exceptions (hard to diagnose failures)
• →No charset control in FileReader/FileWriter (uses platform default — dangerous!)
• →No atomic operations
• →No symbolic link support
• →No file metadata (owner, permissions, timestamps)

java.nio.file solves all of these:

• →Throws IOException with clear messages
• →Explicit charset everywhere
• →StandardCopyOption.ATOMIC_MOVE for atomic file replacement
• →Full symbolic link and attribute support

🏗️ What Happens in Real Projects?

Common enterprise use cases:

• →Reading configuration files (YAML, JSON, properties)
• →Writing reports and exports (CSV, PDF, Excel)
• →Processing uploaded files
• →Log file analysis
• →File-based data pipelines

⚙️ How It Works

Path vs File:

// Legacy
File file = new File("/data/config.json");

// Modern (preferred)
Path path = Path.of("/data/config.json");
Path path2 = Paths.get("/data", "config.json");  // same result

Buffering:

Files.readString() reads the entire file into memory — fine for small files. For large files, use Files.lines() (returns a Stream) or BufferedReader for line-by-line processing without loading everything into memory.

Character encoding:

Always specify charset explicitly. Never use FileReader/FileWriter — they use the platform default charset which varies by OS.

💻 Example

File Operations in Enterprise Java — Common file I/O patterns used in production applications.

// Reading entire file (small files)
Path configPath = Path.of("/etc/myapp/config.json");
String content = Files.readString(configPath, StandardCharsets.UTF_8);

// Reading all lines (small-medium files)
List<String> lines = Files.readAllLines(configPath, StandardCharsets.UTF_8);

// Reading line by line (large files — lazy, memory-efficient)
try (Stream<String> lines = Files.lines(configPath, StandardCharsets.UTF_8)) {
    lines.filter(line -> !line.startsWith("#"))  // skip comments
         .map(String::trim)
         .filter(line -> !line.isEmpty())
         .forEach(this::processConfigLine);
}  // stream closed automatically

// Writing a file (creates or overwrites)
String report = generateReport();
Files.writeString(
    Path.of("/reports/daily-report.txt"),
    report,
    StandardCharsets.UTF_8,
    StandardOpenOption.CREATE,
    StandardOpenOption.TRUNCATE_EXISTING
);

// Appending to a file
Files.writeString(
    Path.of("/logs/audit.log"),
    "User login: " + userId + "
",
    StandardCharsets.UTF_8,
    StandardOpenOption.CREATE,
    StandardOpenOption.APPEND
);

// Writing bytes
byte[] pdfBytes = generatePdf();
Files.write(Path.of("/exports/report.pdf"), pdfBytes);

// Atomic file replacement (safe for config files)
Path tempPath = Path.of("/etc/myapp/config.json.tmp");
Path finalPath = Path.of("/etc/myapp/config.json");
Files.writeString(tempPath, newConfig, StandardCharsets.UTF_8);
Files.move(tempPath, finalPath, StandardCopyOption.ATOMIC_MOVE,
           StandardCopyOption.REPLACE_EXISTING);

🤔 Common Confusions

🚨 Common Production Issues

✅ Best Practices

🏛️ Architect's Note

💬 Frequently Asked Questions

🎯 Key Takeaways

🔗 Related Topics

🎯 Practice this topic in interviews

↗ Where this topic fits