Storage

Object/file storage — images (provider listings), documents, backups. Not the transactional database.

Why we need this / what value this brings

Object storage is built for large, unstructured files (images, documents) in a way a relational DB isn't — using the wrong one for the job costs performance and money.

When to use this

Any file (image, document, export) that doesn't need to be queried like structured data.

How to use or implement this

Store files in object storage (S3-compatible), keep only a reference (URL/key) in the database, not the file bytes themselves.

Research questions

• Where are provider listing images actually stored today — local disk, S3-compatible, or something else?

---

Empty folder — drop notes, links, and findings here as you research.