Hosting execution models

Compare serving files, running functions on demand, and keeping a server running to decide execution and operating responsibilities.

Search within: Hosting execution models

3 field notes

Keep a process listening for requests, with runtime control and responsibility for capacity, supervision and recovery.

Run event-triggered work without owning long-lived compute processes.

Serve prebuilt public files with minimal application operations.

Comparison within this category
Concept	Features	Advantages	Limitations	Suitable situations	Combination conditions
Always-on server	Long-running request listener	Direct runtime control	Supervision and recovery need owners	Custom runtime behavior	External durable store and static frontend
Serverless functions	Event-triggered managed handlers	Platform handles server provisioning	Retries and lifecycle need design	Event-oriented APIs	Static frontend plus external storage
Static hosting	Prebuilt file delivery	Reading needs no app renderer	Personal writes need an API	Public articles and documentation	Static generator plus server or function