Avatar Metadata Search: Keep Object Storage for Bytes, Catalog for Queries
The article argues that object storage should hold avatar bytes under immutable, addressable keys, while content type, tags, ownership, and moderation state belong in a queryable catalog. Bucket prefix listing suits repair and audit tasks but cannot efficiently evaluate predicates such as type plus tags within a tenant. The author notes that declared Content-Type headers are only hints and should be verified by inspecting the payload with a bounded decoder. A catalog row with explicit ready, pending, and failed states can bridge the lack of atomic commits between database and bucket. The piece also names failure modes such as orphan objects, dangling rows, duplicate retries, and stale current pointers.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in