Why is Composite often used in file systems?

Composite is often applied in file systems because their structure is hierarchical, and files and folders need to be handled the same way.

---

#1. A Natural Tree Structure

Folders contain other elements (files and subfolders), while files are terminal nodes. This is the classic "container + elements" model, a perfect fit for Composite.

---

#2. A Single Interface for Operations

Both files and folders implement the same interface, for example:

This lets you call the same methods without checking the type:

---

#3. Recursive Actions

Composite simplifies operations that must run recursively: deleting a folder, computing its size, searching. Each element decides for itself how to handle the request: a leaf performs the action, a container delegates it to its children.

---

#4. Extensibility

You can easily add new element types (for example, an archive or a symbolic link), as long as they support the same interface.