Block storage vs object storage vs file storage in HLD - Architecture Patterns Compared

System Overview - Block storage vs object storage vs file storage

This system explains three common types of data storage: block storage, object storage, and file storage. Each type stores data differently and is suited for different use cases like databases, backups, or shared files.

Architecture Diagram

User
  |
  v
+-----------------+       +-----------------+       +-----------------+
| Block Storage   |<----->| File Storage    |<----->| Object Storage  |
| (Raw Data Blocks)|       | (Hierarchical)  |       | (Metadata + Data)|
+-----------------+       +-----------------+       +-----------------+

Components

Block Storage

storage

Stores raw data in fixed-size blocks, ideal for databases and virtual machines.

File Storage

storage

Stores data as files in folders with a hierarchy, suitable for shared file systems.

Object Storage

storage

Stores data as objects with metadata and unique IDs, good for backups and large unstructured data.

Request Flow - 3 Hops

User → Block Storage

User → File Storage

User → Object Storage

Failure Scenario

Component Fails:Block Storage

Impact:Data blocks may become inaccessible or corrupted, affecting databases or VMs.

Mitigation:Use replication and backups; implement RAID or distributed block storage systems.

Architecture Quiz - 3 Questions

Which storage type stores data as fixed-size blocks without metadata?

A Block Storage

B File Storage

C Object Storage

D Cloud Storage

Design Principle

This architecture shows how different storage types serve different needs by organizing and accessing data differently: block storage for low-level fast access, file storage for shared hierarchical files, and object storage for scalable metadata-rich data.