How VAST DataBase works inside, as far as it changes the code you write. Start with The cluster underneath (DASE), which explains the Element Store that tables share with files and objects, then Table structures and Read path and pruning; read Write path and Transactions when you tune loads or handle conflicts.
- The cluster underneath (DASE): DASE and the Element Store explained for builders: one store for files, objects and tables, write durability, data reduction and replicas.
- How tables are stored: How a table is laid out: row groups, separately stored columns, per-chunk min/max statistics and hidden row markers, and why it matters.
- Write path: What happens to rows after inserts, imports, updates, deletes and column changes, and why some loading patterns behave better than others.
- Read path and pruning: What the cluster does for a query, and how min/max statistics, sorting, projections and partitions decide how much it skips.
- Transactions: What a transaction sees, when its changes become visible, which transaction wins a write conflict, and what happens to transactions left open.
- Table structures: Regular, sorted, partitioned, semi-sorted projection and vector-indexed table layouts: what each is, what it buys you, and how row IDs differ.
- Compression and data reduction: Why tables have no codec setting, how cluster data reduction applies to them, and what the Trino and Spark compression options do.