> 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/c/cluster.md). # Cluster A group of servers and other resources that act like a single system and enable high availability and, in some cases, load balancing. A cluster is a group of interconnected computers or servers that work together as a unified system to provide higher availability, improved performance, or both. Clusters distribute workloads across multiple nodes, so if one node fails, others can take over its responsibilities. Clusters are commonly used in database systems, application servers, and container orchestration platforms like Kubernetes. They can be configured for high availability (failover clusters), load balancing (distributing traffic across nodes), or high-performance computing (parallel processing of large workloads). In API infrastructure, clustering ensures that backend services remain available even during hardware failures or traffic spikes. While serverless platforms abstract away cluster management from developers, the underlying infrastructure still relies on clusters. API gateways themselves may be deployed as clusters to handle high request volumes and provide zero-downtime deployments. --- # 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/c/cluster.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.