StatelessProcesses [rule] v1.0.0

App processes are stateless and share-nothing. Any data that must persist is stored in a stateful backing service (database, cache, object store). Memory and local disk may be used as a brief, single-transaction scratchpad — never as a durable store across requests.

Checks

• No in-memory session store. Sessions go to Redis, Memcache, or a DB.
• No 'sticky sessions' assumption. Any request can be served by any process instance.
• Local filesystem and tmp are scratch only — assume the process restarts at any time and disk is lost.
• Long-lived in-memory caches are advisory; data must also exist in a backing service.

Label

Processes are stateless and share-nothing

StatelessProcesses [rule] v1.0.0

App processes are stateless and share-nothing. Any data that must persist is stored in a stateful backing service (database, cache, object store). Memory and local disk may be used as a brief, single-transaction scratchpad — never as a durable store across requests.

Checks

• No in-memory session store. Sessions go to Redis, Memcache, or a DB.
• No 'sticky sessions' assumption. Any request can be served by any process instance.
• Local filesystem and tmp are scratch only — assume the process restarts at any time and disk is lost.
• Long-lived in-memory caches are advisory; data must also exist in a backing service.

Label

Processes are stateless and share-nothing

Relations

enhances: [@backend-architecture/principle-disposability, @backend-architecture/principle-concurrency-process-model]

Label

Processes are stateless and share-nothing

Enhances

• @backend-architecture/principle-disposability
• @backend-architecture/principle-concurrency-process-model