The name shows the glue: a first version is often a villager's work dressed as a town planner's

Naming a service as ephemeral, town planner and a service makes you ask whether it is really a commodity or only looks like one, and plenty of things sold as commodities are a large amount of custom technology glued together behind the scenes. Lambda, the definition of serverless for most people, ran on Linux containers inside EC2 instances for its first four years, until Firecracker replaced them from 2018, in its builders' own words. A per-hour bill for a 'serverless' product usually means the provider cannot yet spin the thing up and down fast and safely enough to bill by use: an engineering gap on their side, passed to you as a cost. Not a criticism, that is how services become commodities, and the floors that halve and the scale-to-zero that arrives are the record of it maturing in public.

Decided by. Nobody yet: a candidate for Dinis to read, comment on and decide (keep, rewrite, merge, cut, article first, later, not doing it).

Note. Could also serve where-do-you-land as a worked example of a Wardley map showing what sits behind a commodity. Werner Vogels is quoted: AWS delivers 'new services often with a minimal feature set' and lets customers 'help drive the roadmap'. The Firecracker account is AWS's own (NSDI 2020). Wardley in 2016: 'It's not really serverless but more I don't care what a server is.'

Where it comes from

Ephemeral town planner services The test; The glue behind the commodity (newsroom)

What it answers in the 2018 book

Serverless answered outline, Concepts
Are you a pionner, Settlers or Town Planners answered outline, Life Patterns

Where it goes

Chapter Serverless, for real, part Build it without a server (drafting); topic Explorers, villagers and town planners (Wardley's frame).

Other ideas proposed for the same chapter: Building blocks: cloud as Lego, free models with your own key, git as a standard, The file system is the database: load, extract, transform, save, and keep every intermediate as a file, 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, What serverless costs when nobody is using it, product by product, 18 October 2026, Move the cloud, not the code: a twin the application cannot tell from the real service.

Node idea:the-glue-behind-the-commodity in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.