HTTP-Based Access Model
What you'll learn: How object storage uses standard web protocols (HTTP) and RESTful APIs to let you perform CRUD operations on your objects.
Understanding HTTP and RESTful Access
Unlike block storage (which attaches to VMs like hard drives) or file storage (which uses network file protocols), object storage works over the same HTTP protocol that powers the web. When you want to interact with objects in a bucket, you send standard HTTP requests—just like your web browser does when loading a webpage.
The Four Core HTTP Methods
Object storage uses RESTful API principles, mapping familiar HTTP verbs to CRUD operations:
- GET: Retrieve (read) an object from a bucket
- PUT: Create or update (write) an object
- DELETE: Remove an object
- HEAD: Get metadata about an object without downloading it
How It Works in Practice
Think of object storage like a global filing cabinet accessible via web requests. Instead of physically connecting a storage device, you make HTTP calls:
- Need to store a backup file? Send a
PUTrequest to your bucket with the file as the payload - Want to download a customer invoice? Make a
GETrequest using the object's key - Removing old logs? Issue a
DELETErequest for that object - Checking if a file exists or how large it is? Use
HEADto retrieve just metadata
Because it's HTTP-based, any programming language or tool that can make web requests can interact with object storage. You can access objects via SDKs, command-line tools, or even directly from web browsers using pre-signed URLs.
Key Takeaway: Object storage uses standard HTTP methods (GET, PUT, DELETE) in a RESTful API model, making CRUD operations simple and universally accessible from any web-enabled client.