← Graph

SQLite as Deployment Artifact

concept 1 connections

Vaporware idea in the Yippee talk: combine Bootsnap's trick of caching Ruby VM instructions with SQLite's 'faster than the file system' property by having the build write all pre-parsed VM instructions into a single SQLite database file, then ship that one file as the deployment artifact. A single large file is easier (and likely faster) to transmit reliably over HTTP than hundreds of small files, and removes partial-deploy failure modes.

category
architecture
about
SQLite as Deployment Artifact concept
Full-vaporware idea of writing Ruby VM instructions to a SQLite file and shipping that single file as the deploy artifact.

Provenance

Read by
1 extraction