method candidate goes to: this-edition T town planner
The file system is the database: load, extract, transform, save, and keep every intermediate as a file
A database server is a large, stateful, always-on thing to provision, secure, back up and pay for, and most of what it holds would be happy as files. LETS loads state, works on it and saves every stage back as files you can version, diff and read: a cache, a database and an audit trail in one, with git as its history. Two real database engines now run in the reader's browser over the site's own JSON.
Decided by. Nobody yet: a candidate for Dinis to read, comment on and decide (keep, rewrite, merge, cut, article first, later, not doing it).
Where it comes from
- No server, by design Step one: the file system is the database (newsroom)
What it answers in the 2018 book
- Serverless answered outline, Concepts
Where it goes
Chapter Serverless, for real, part Build it without a server (drafting); topic Building blocks: cloud, serverless, free models, git and CI.
Other ideas proposed for the same chapter: Building blocks: cloud as Lego, free models with your own key, git as a standard, No server, by design: retire the back end too, and keep only commodity servers, Ship now, and ship your startup serverless: no servers of yours, no database, client side, with privacy by design and control of your agents.
Node idea:the-file-system-is-the-database in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.