[aclatuts]

This makes perfect sense for a headless CMS. An editor might upload changes or a new article a few times per day/week into a database through a headless CMS. A webserver could make a request to the headless CMS/database for every web page load, but if the content doesn't change then the webpage can be computed and served statically. The web server can compute just the changes per page or regenerate the whole site on any change on the backend.

[omnimus]

You can also simply call it caching and put that rendered html in cache inside or even outside your system and you get the same thing.