> 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/r/redundancy.md). # Redundancy The duplication of critical components or functions of a system with the intention of increasing reliability of the system. Redundancy is the practice of duplicating critical system components so that if one fails, another can take over without service interruption. Redundancy can apply to hardware (multiple servers, power supplies, network links), software (multiple instances of an application), and data (replicated databases, backup copies). Types of redundancy include active-active (all copies handle traffic simultaneously), active-passive (standby copies activate only on failure), and N+1 (one spare for every N active components). Geographic redundancy distributes copies across different physical locations or data centers to protect against regional failures. In API infrastructure, redundancy is essential for maintaining availability. API gateways deployed across multiple regions or edge locations provide geographic redundancy, ensuring that if one location fails, requests are automatically routed to the nearest healthy location. Backend services behind the gateway should also be redundant. Serverless platforms provide built-in redundancy by running functions across multiple availability zones or edge nodes, removing the need for teams to manage redundancy configurations manually. --- # 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/r/redundancy.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.