[wernst]

Triplit has migrated its data format away from triples since this post was authored, so the memory concerns mentioned are no longer relevant since 1.0 https://www.triplit.dev/blog/triplit-1.0 (source: i'm Triplit author). I don't think triples as a format are inherently bad but for us it did entail more data on disk, more difficult and slower querying, and more objects in the JS heap ballooning RAM.

[GermanJablo]

Now you're storing all the rows as units, right? When users create tables in Triplit, do they end up with really different tables or are they more more like a single table of content in json + table_meta_ref? I would love to know more about architecture and the changes that you have made