Serving
What is HTTP serving for tables?
HTTP serving exposes insert, query, and computed results as routes from the same schema that defines the tables.
Updated
How it works
- Routes are declared next to the classes.
- An insert route writes a row, which runs computed columns.
- A query route returns rows.
What it is not
It is not a separate web app that copies rows into another store, and it is not a backend that provisions a scalar database plus auth.
HTTP serving: this, and the thing it is confused with
| This | Not this | |
|---|---|---|
| Defined with | The tables | A second service |
| Insert | Runs the columns | Writes a row someone else processes |
| Auth and CRUD hosting | Not this | A backend-as-a-service |
Where Pixeltable fits
Pixeltable declares routes with FastAPIRouter on the same file as the tables. pxt service update starts them.
Questions
- How does HTTP serving work?
- Routes are declared next to the classes. An insert route writes a row, which runs computed columns. A query route returns rows.
- What is HTTP serving often confused with?
- It is not a separate web app that copies rows into another store, and it is not a backend that provisions a scalar database plus auth.