> 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/stress-testing.md). # Stress Testing A form of deliberately intense or thorough testing used to determine the stability of a given system or entity. Stress testing is a type of performance testing that evaluates how a system behaves when pushed beyond its normal operating capacity. The goal is to identify the system's breaking point, observe how it fails (gracefully or catastrophically), and verify that it recovers properly once the load subsides. Unlike load testing, which verifies performance under expected traffic volumes, stress testing intentionally exceeds those limits. Testers gradually increase the request rate, number of concurrent connections, or payload sizes until the system degrades or fails. This reveals bottlenecks such as memory leaks, connection pool exhaustion, database lock contention, and inadequate timeout configurations. For API systems, stress testing validates that the API gateway, backend services, and databases can handle traffic spikes without data loss or extended outages. It also verifies that protective mechanisms like rate limiting, circuit breakers, and auto-scaling respond correctly under extreme conditions. Serverless platforms have their own concurrency and rate limits, and stress testing helps teams understand these boundaries and configure appropriate safeguards. --- # 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/stress-testing.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.