What is objectstorage?

Object storage is a way of saving data where each piece of information is kept as a self‑contained “object.” An object includes the raw data itself, some descriptive information called metadata, and a unique identifier. Unlike traditional file systems that use folders and hierarchies, object storage puts everything in a flat space called a bucket or container.

Let's break it down

  • Object: the file you upload plus its metadata (size, type, creation date, etc.).
  • Bucket: a container that holds many objects; think of it as a big folder.
  • Key: the unique name or ID that lets you retrieve a specific object.
  • Metadata: extra details you or the system attach to an object, useful for searching and managing data.
  • API/Interface: you talk to object storage over the internet using simple commands (REST, S3 API, etc.) instead of mounting a drive.

Why does it matter?

Object storage lets you keep massive amounts of data without worrying about running out of space or managing complex directory trees. It is built to be highly durable (often 99.999999999% durability) and can automatically copy data across many locations, protecting it from hardware failures. Because you pay for what you store and retrieve, it can be cheaper than traditional storage for large, infrequently accessed files.

Where is it used?

  • Storing backups and disaster‑recovery copies.
  • Hosting media files such as photos, videos, and audio for websites or apps.
  • Keeping big‑data sets for analytics and machine‑learning pipelines.
  • Serving static assets for web sites (images, CSS, JavaScript).
  • Archiving logs, documents, and compliance records. Popular services include Amazon S3, Google Cloud Storage, Microsoft Azure Blob Storage, and IBM Cloud Object Storage.

Good things about it

  • Scalability: grow from gigabytes to petabytes without re‑architecting.
  • Durability & Redundancy: data is automatically replicated across multiple devices or locations.
  • Simple Access: retrieve objects via HTTP/HTTPS using a single key.
  • Cost‑Effective: pay‑as‑you‑go pricing, especially for infrequently accessed data.
  • Metadata‑Rich: custom tags make searching and lifecycle management easy.

Not-so-good things

  • Higher Latency: retrieving a single small file can be slower than a local disk.
  • Eventual Consistency: after a write, it may take a short time before all reads see the new data.
  • Not Ideal for Frequent Updates: object storage works best for write‑once, read‑many scenarios, not for constantly changing files.
  • Limited POSIX Features: you can’t mount it like a traditional file system for random‑access reads/writes without extra tools.
  • Potential Egress Costs: moving data out of the cloud can incur additional fees.