Short answer: put the generated image in private object storage and keep the game’s searchable state in a relational database. That split is the better default because images are large, unstructured binary objects, while ownership, moderation, provenance, and deletion state need relational queries and transactions. The real decision is governance: who can read the bytes, which processor retains them, and how an asset disappears.
I would evaluate this as a reliability boundary before comparing storage features. A BLOB column can hold an image. The harder question is what happens when a player loses access, a generation is retried, or a studio requests deletion. The design below makes those events explicit, then compares providers on the controls they actually expose.
For this workflow, Infrai belongs between the Python backend and private object storage: its storage surface can handle the object write, while the game remains responsible for authorization and its relational record.…