Object Storage: Data Without a File Hierarchy
Object storage is like a valet system for data. You get a unique ID for a self-contained 'blob' of data and metadata, instead of navigating a file path. It's the backbone of cloud storage (like S3) for images and backups. The footgun: objects are immutable.
Why it exists
Traditional file systems, with their nested folders, struggle at massive scale. Managing the hierarchy and metadata across many machines becomes a bottleneck. Object storage was created to handle vast amounts of unstructured data by flattening the structure and making each object a self-sufficient unit.
The mental model
Imagine a giant, single-level warehouse where every box has a unique barcode. The box contains your item (the data) and a packing slip (the metadata). To get your item, you don't need to know its aisle or shelf number; you just present the barcode (the object ID) at the front desk. This is unlike a file system, which is like a multi-story building with rooms and folders you must navigate through.
How it works
Data is stored as an "object" or "blob". Each object consists of three parts: the data itself (e.g., a JPEG file), variable metadata (e.g., image resolution, creation date), and a globally unique identifier. The system uses this ID to locate and retrieve the object from a massive, flat address space that can span many physical servers. The storage system itself manages data replication and distribution for durability and availability, abstracting the physical hardware away from the application.
When to use it
Use object storage for write-once, read-many workloads with large, static files. It's ideal for storing user-generated content like images and videos, website assets, backups, archives, and data for big data analytics. Cloud services like Amazon S3, Google Cloud Storage, and Azure Blob Storage are canonical examples.
When not to use it
Avoid object storage for data that requires frequent, low-latency updates, like a transactional database or the operating system files for a server. Since objects are immutable, changing even one byte requires re-uploading the entire object, which is slow and inefficient for these use cases. Block storage is a better fit for databases and OS volumes.
One canonical example
A web application lets users upload profile pictures. The application saves the image file to an object storage bucket (like AWS S3). It receives a unique URL/ID for the object, which it then stores in the user's database record. When another user views the profile, the web page simply references that URL to load the image directly from the object store, bypassing the web server.
Interview question
Why is object storage generally not recommended for applications requiring frequent, small updates to data, such as a transactional database?
- a.Its flat structure makes navigating and locating specific data blocks inefficient for rapid changes.
- b.The overhead of generating globally unique identifiers for each small update is too high.
- c.It lacks the ability to manage file permissions and access control at a granular level.
- d.Objects are immutable, meaning even a small modification necessitates replacing the entire object.Correct
Why? this is the answer
The card explicitly states that objects are immutable, making object storage unsuitable for frequent updates because changing even one byte requires re-uploading the entire object. While other options might seem plausible, the immutability is the direct and primary reason given in the card.
Just read this? Test yourself on what you have been reading.
Read the original → en.wikipedia.org
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on storage — each one lists the topics its interview covers.
See open roles