Every byte an app saves ends up in one of three shapes: a file in a folder, a numbered block on a disk, or an object in a bucket. The shape you pick decides how fast you can read the data, how far it can grow and what it costs to keep.
Three ways to organise the same data
File, block and object storage can all hold the same photo or the same database. What differs is how the data is addressed: how you tell the storage system which piece you want.
- File storage addresses data by a path, such as
/recipes/tuna/pie.txt. - Block storage addresses data by a block number on a volume.
- Object storage addresses data by a unique key in a flat bucket.
Everything else, from speed to price to what each is good at, follows from that choice.
File storage: folders and paths
File storage is the model you already know from your laptop. Data lives in files, files live in folders, and folders sit inside other folders to form a tree. To read something, you give its path, and the system walks the tree to find it.
On a network, the same idea is shared between machines. A file server (often called NAS, network-attached storage) exposes a folder tree over a protocol such as NFS or SMB, and many servers can mount it at once. Managed cloud versions exist too, such as Amazon EFS or Azure Files.
Why people like it
- It is easy to understand. People and programs both know how to work with paths.
- It supports the operations apps expect: open, read part of a file, append, rename, lock.
- Several machines can share one folder tree, which suits shared documents, home directories and tools that expect a normal disk.
Wondering how this was made? How we make these