Depends on how you define "stateful": - Are long-lived per-process in-memory read-through caches "stateful"? - Is per-connected-websocket topic subscription s

Depends on how you define "stateful": - Are long-lived per-process in-memory read-through caches "stateful"? - Is per-connected-websocket topic subscription state "stateful"? In both of these cases, nothing breaks when you hard-kill + restart one of these processes. People who add these things to a web-app backend don't usually think of themselves as making the backend "stateful." But nevertheless, truly "stateless" technologies like CGI or PHP are defined by how they don't have access to things like this.