Storage

Block vs object vs file storage: what's the difference?

Block, object and file storage explained: how each one finds your data, why databases run on block volumes, and why photos and backups live in S3-style buckets.

  • 8 min read
  • 5 questions
  • +35 XP
Transcript

Block, Object and File Storage, explained by cats. Kitty has a lot of tuna recipes. She needs to store them somewhere. There are three main ways to store data. File. Block. And Object. First, File Storage. File storage is the simplest.

Think of a big filing cabinet. Folders inside folders. Kitty knows exactly where everything lives. Easy to navigate. Easy to understand. But hard to scale when the cabinet gets huge. Second, Block Storage. Block storage is different. No folders. No hierarchy.

Data is split into fixed chunks called blocks. Each block gets an address. Kitty doesn't see files. She sees raw blocks. It's fast. Very fast. Perfect for databases and virtual machines. But Kitty needs extra software to make sense of the blocks.

Lastly, Object Storage. Object storage is the newest. No folders. No blocks. Everything is a flat object. Each object has data, a unique ID, and metadata. Metadata is extra info. Like tags on a tuna can. Kitty doesn't navigate to it.

She just asks for it by ID. Infinitely scalable. Cheap. Slow to update. Perfect for photos, videos, backups. This is how S3 works. File storage is organised but limited. Block storage is fast but complex. Object storage is scalable but simple.

Kitty picks based on the tuna. Same data. Different ways to store it. Pick the right one and Kitty is happy.