✳flâneur — a map of the web's best reading

The Baked Data architectural pattern

simonwillison.net · 1,971 words · saved by 1 readers

I’ve been exploring an architectural pattern for publishing websites over the past few years that I call the “Baked Data” pattern. It provides many of the advantages of static site generators while avoiding most of their limitations. I think it deserves to be used more widely. I define the Baked Data architectural pattern as the following: Baked Data: bundling a read-only copy of your data alongside the code for your application, as part of the same deployment Most dynamic websites keep their code and data separate: the code runs on an application server, the data lives independently in some kind of external data store—something like PostgreSQL, MySQL or MongoDB. With Baked Data, the data is deployed as part of the application bundle. Any time the content changes, a fresh copy of the site is deployed that includes those updates. I mostly use SQLite database files for this, but plenty of other formats can work here too. This works particularly well with so-called “serverless” deployment

The Baked Data architectural pattern Simon Willison’s Weblog Subscribe Sponsored by: Microsoft - Agent projects stall between demo and production. Microsoft's MVP checklist closes that gap. Try it The Baked Data architectural pattern 28th July 2021 I’ve been exploring an architectural pattern for publishing websites over the past few years that I call the “Baked Data” pattern. It provides many of the advantages of static site generators while avoiding most of their limitations. I think it deserves to be used more widely. I define the Baked Data architectural pattern as the following: Baked Dat

Explore this link on the map →

saved by

related reading