File system
A file system is a software-managed structure and interface for organizing, naming, storing, and accessing files and directories on storage.
Amazon Web Services in Action, Third Edition: An in-depth guide to AWS
A filesystem is a data-management structure that organizes blocks into files and directories for operating-system access.
- How it is used
- Supports legacy applications and databases that expect operating-system file system calls instead of object-storage APIs.
- How deep it goes
- Explains path translation, system calls, filesystem creation, mounting, persistence, and shared-storage trade-offs without detailing filesystem internals.
- Examples
- Uses Linux commands to inspect, format, mount, verify, unmount, detach, reattach, and remount an EBS volume.
- What you can do after
- Operate/configure an EBS-backed file system and select EBS, instance store, or EFS for an application’s access pattern.
Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform
File storage is a persistent storage mechanism that organizes data as files.
- How it is used
- Adds persistent locations for application assets and keeps storage responsibilities separate from video streaming.
- How deep it goes
- Explains provider-backed storage, service abstraction, local replacement, mounted directories, and stream-based file operations.
- Examples
- Uses Azure Storage, a video-storage service, a mock-storage service, local video files, and Docker Compose volume mounts.
- What you can do after
- Operate/configure storage through a dedicated service and substitute local filesystem storage for cloud storage during development.
Kubernetes in Action, Second Edition
A filesystem is a structure and set of operations for organizing, storing, and accessing files, including the isolated filesystem presented to a container.
- How it is used
- Explains how containers store files, preserve data across replacement, share selected paths, and access node filesystems.
- How deep it goes
- Defines isolation, mounting, persistence, and mount namespaces, then demonstrates hostPath usage without detailing filesystem implementation internals.
- Examples
- Uses container restarts, shared pod volumes, and kube-proxy hostPath mounts for /run/xtables.lock and /lib/modules.
- What you can do after
- Operate/configure container storage by mounting volumes for persistence or sharing and exposing node paths through hostPath.
Read how Kubernetes in Action, Second Edition explains file system →
100 Java Mistakes and How to Avoid Them
A filesystem is a system that organizes and provides access to files and directories on storage or through a mounted hierarchy.
- How it is used
- Uses filesystem operations to illustrate flaky tests, race windows, and safer file-handling patterns.
- How deep it goes
- Explains separate queries, combined attributes, and bounded reads, but treats replacement races as corner cases rather than internals.
- Examples
- Uses backup-folder time checks, file-type and size queries, and maximum-size file reads.
- What you can do after
- Apply safer Java NIO file handling by combining metadata queries and enforcing size limits during reads.
Read how 100 Java Mistakes and How to Avoid Them explains file system →
Related concepts
- copy instructionused by · The Dockerfile COPY instruction copies files or directories from a build context or another build stage into an image’s filesystem.
- bind mountused by · A bind mount makes an existing file or directory accessible at another filesystem location, commonly exposing host contents within a container.
- monitoringused by · Monitoring is the ongoing observation and measurement of a system’s behavior, state, or operational signals to assess its condition and detect changes or problems.
- container securityaddressed by · Container security is the practice of protecting container images, runtimes, workloads, hosts, configurations, and supporting infrastructure from vulnerabilities, compromise, and unauthorized activity.
- WASIused by · WASI, the WebAssembly System Interface, is a standardized collection of interfaces that enables WebAssembly programs to access operating-system-like resources portably.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.