Serving
What is a multimodal backend?
A multimodal backend is storage, orchestration, retrieval, and HTTP for media and models in one deployable schema.
Updated · Part of What is HTTP serving for tables?
How it works
- One file declares the tables and the routes.
- Inserts run the models.
- Clients call HTTP or insert rows directly.
What it is not
It is not object storage plus a vector database plus a job runner plus an API gateway, wired by hand.
multimodal backend: this, and the thing it is confused with
| This | Not this | |
|---|---|---|
| Pieces | One schema | Four services |
| Sync | Row update | Glue jobs |
| Client | HTTP or a script | A different SDK per service |
Where Pixeltable fits
Pixeltable is that backend: database, computed columns, and serving in one Python file.
Questions
- How does multimodal backend work?
- One file declares the tables and the routes. Inserts run the models. Clients call HTTP or insert rows directly.
- What is multimodal backend often confused with?
- It is not object storage plus a vector database plus a job runner plus an API gateway, wired by hand.