> 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/e/elasticity.md). # Elasticity The ability of a system to automatically scale resources up or down as needed. Elasticity is the ability of a computing system to automatically provision and deprovision resources in response to changing demand. An elastic system scales out (adds resources) during traffic spikes and scales in (removes resources) when demand decreases, optimizing both performance and cost. Elasticity differs from scalability in an important way: scalability is the capability to handle increased load, while elasticity is the ability to do so automatically and dynamically. Elastic systems are typically cloud-based, leveraging the on-demand nature of cloud infrastructure to adjust capacity without manual intervention. Serverless platforms provide inherent elasticity. Functions are invoked on demand and scale automatically with the number of incoming requests, with no pre-provisioned capacity. API gateways deployed on serverless platforms like Cloudflare Workers inherit this elasticity, handling traffic ranging from zero to millions of requests without capacity planning. This pay-per-use model eliminates over-provisioning costs while ensuring availability during unexpected traffic surges. --- # 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/e/elasticity.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.