Skip to content

Tessera DB

PX-01

View 03

JSON in, the same record out — and files kept next to the rows.

Load JSON documents and each becomes a record the graph, SQL and search read too. Store a photo or a PDF next to the rows it belongs to, and it survives a restart and is in every backup.

01

03

View 03 · Documents

A document is a record, not a second database.

A document store beside a graph database is two copies of the customer. Here a JSON document is loaded once; its fields are columns for SQL, its links are edges for the graph, and its text is in the search index.

64 MiB

Per import body

1

Copy of each document

0

Sync jobs

02

03

What it does.

01

JSON import

POST /api/import/json loads rows and graph links in one body; POST /api/documents inserts a document. Each load records a receipt of what was written and refused.

02

Records need not match

Records of one type need not all have the same fields. A field only some records carry is a real column and reads NULL on the others.

03

Files next to the rows

Upload any file to /api/files. It streams to the server's data folder, survives a restart and is in every backup; downloads support Range requests and signed URLs.

03

03

Not yet.

01

A MongoDB-compatible door

Planned, not in 1.0. Documents are loaded and read over HTTP today.

Tessera DB is live.