The Baked Data architectural pattern

It's really fun seeing how Mozilla.org use this pattern (they started using it long before I tried to coin a name for it) - they distribute a SQLite DB file containing the site content to all of their application servers, and you can download a copy from their healthcheck page: https://www.mozilla.org/healthz-cron/

Paul McLanahan wrote more about this works here: https://mozilla.github.io/meao/2018/03/28/bedrock-the-sqlite...

My blog is set up this way, but with markdown files instead of SQLite. At startup the server loads the whole database of posts into memory and then writes rendered pages out to disk as they're requested using a gem called Rack::FunkyCache. Nginx sits in front and serves the cached files once they've been generated.

I've been toying with loading the pages into SQLite to facilitate search for awhile. Thanks for the reminder!

Crazy idea for lispers: Bake your data into the image, preferably with something like :PURIFY T if it helps.