File system and path APIs — Node.js & Express Backend

The file system is a fundamental resource in every backend application. Whether you are reading configuration files at startup, writing log entries, storing user uploads, processing CSVs, or managing temporary files during data transformations, the fs and path modules are in constant use. Node.js exposes the file system through three programming models in the fs module: the legacy callback-based API (fs.readFile with a callback), the newer Promises API (fs.promises.readFile or the promises-ready import via require('fs').promises), and the synchronous API (fs.readFileSync). The path module provides platform-safe utilities for constructing, parsing, and normalising file paths — a category of errors that silently produces wrong behaviour on Windows versus Linux if done naively with string concatenation. Understanding when to use each fs API variant and how to build paths correctly is not merely stylistic — mistakes in this area cause data corruption, path traversal security vulnerabilities, and cross-platform bugs that only surface in production deployments.

Analogy🏏Cricket

🏏 Think of it like cricket: In a Test match, there are multiple types of scheduled breaks and interruptions, each with different priority levels and timing rules. The lunch break (setTimeout) is scheduled for a specific time but can be delayed if a wicket falls just before — it fires at the next available opportunity after its scheduled time, not at the exact scheduled time. The drinks break (setImmediate) is taken at the end of the current over, as soon as the ongoing delivery sequence finishes. The umpire's over-rate check (process.nextTick) happens immediately after each delivery, before the next batsman faces — it cannot be deferred. The DRS review resolution (Promise microtask) happens between deliveries, after the umpire check but before any scheduled breaks. Just as the match referee would be furious if an umpire kept conducting over-rate checks after every single ball indefinitely (starving nextTick), the event loop is unable to proceed if process.nextTick callbacks keep registering new nextTick callbacks recursively. The insight is that each timer primitive is not just a delay mechanism — it is a specific position in a formal protocol, and misusing it violates that protocol's invariants.