> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/s/state.md). # State In computing, the condition or quality of a computing system as stored in its temporary memory locations or registers. In computing, state refers to the stored information that a system, application, or component maintains at a given point in time. This includes data in memory, variables, database records, session information, and any other data that reflects the current condition of the system. State changes as the system processes requests and events. State management is a fundamental challenge in distributed systems. Stateful systems store data locally and depend on that data for subsequent operations, which complicates scaling and failover. Stateless systems treat each request independently, with no reliance on locally stored data, making them easier to scale and distribute. In API and serverless architectures, managing state is a key design consideration. Serverless functions are inherently stateless -- they do not retain data between invocations. State must be stored externally in databases, key-value stores (like Cloudflare KV or Redis), or object storage. API gateways are also typically stateless, processing each request independently. This stateless design enables horizontal scaling and geographic distribution, but requires careful planning for features that depend on state, such as rate limiting counters and session tracking. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.serverlessapigateway.com/glossary/s/state.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.