stateless process
A process that keeps nothing it needs between requests in its own memory or disk, so it can be restarted or replaced at any moment.
In more detail
Factor VI of the twelve-factor app: processes are stateless and share-nothing, and anything that must persist lives in a stateful backing service such as a database. Memory and local disk may serve only as a brief single-transaction cache. Stateless processes are what make horizontal scaling and disposability possible.
Related terms
- backing service — Any service an application uses over the network, such as a database, cache, queue, mail relay or payments provider.
- sticky session — A load balancer setting that sends every request from one client to the same server copy, usually because that copy holds its state in memory.
- horizontal scaling — Handling more load by running more copies of a process, often on more machines, rather than making one machine bigger.
- disposability — The property of a process that can be started or stopped at a moment’s notice without harm.
Taught in
- Build, Release, Run And Processes — DevOps & Site Reliability Engineering
- Port Binding And Concurrency — DevOps & Site Reliability Engineering