177
object storage
Blobs addressed by key. Not a filesystem, not a database, not something you append to in place.
What is object storage?
Object storage keeps immutable-ish blobs (files) behind an API. You PUT an object. You do not seek and overwrite a byte. Consistency and listing have limits. It is the right place for uploads, images, and data lake files. It is the wrong place for a lock or a counter.
Why does object storage matter when vibe coding?
Models save uploads on the local disk of the web server. The next instance cannot see them. Name the bucket and the key layout.
How do you do object storage?
PUT the object. Store the key in the database, not the bytes. Serve via signed URLs if private. Never use the bucket as a query engine.
How do you ask a model for object storage?
Store (files) in object storage, not on local disk. Save the key in the database. Serve private objects with signed URLs that expire. Do not list the whole bucket to find one user’s files — index the keys.
What goes wrong with object storage?
A signed URL that never expires, leaked in a log. Bound the lifetime. Do not sign with a world-readable key.