> For the complete documentation index, see [llms.txt](https://www.axisnow.io/zh/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.axisnow.io/zh/docs/security/service-reliability.md).
# 服务可靠性
AxisNow 如何在可用性、性能和可扩展性上保障服务可靠性
## **AxisNow 的基础设施和服务有多可靠？**
**服务可靠性**是信息安全的核心方面。本文档描述了 AxisNow 如何在可用性、性能和可扩展性方面确保服务可靠性。由于我们架构和部署基础设施及软件的方式，AxisNow 提供了优于传统解决方案的可靠性。
***
## **可用性**
我们以可靠性为首要任务，设计平台，确保您的应用程序持续可用且无缝运行。通过分布式架构、自动故障转移机制和实时监控，我们最大限度地减少停机时间并降低潜在的中断风险。我们主动的事件管理和容错方法，确保您的关键工作负载即使在面临意外挑战时也能保持正常运行。
* **使用世界级基础设施提供商**：我们使用 AWS 托管核心组件。AWS 采用的技术支持 AWS 自身应用程序，服务于数十亿用户。
* **实施容错、冗余基础设施**：我们的服务从多个数据中心提供，这些数据中心互为镜像。如果一个数据中心出现可用性问题，其他数据中心将自动接管负载。
* **使用地理分离的多个数据中心**：这降低了环境灾害和其他地点特定灾难的风险。
* **提供服务状态透明度**：客户可在 status.axisnow\.io 监控服务状态。
* **提供针对 DDoS 攻击的韧性**：我们实施某些措施以减轻 DDoS 攻击的风险。
* **7 x 24 监控**：我们使用多种自动化工具全天候监控服务，并在出现任何服务可用性问题时向我们发出警报。
***
## **性能和可扩展性**
无论您的业务规模，我们的系统都能实时调整，确保在任何规模下都能提供最佳性能和流畅的体验。随着您应用程序访问需求的增长，我们的平台可以轻松扩展，以满足日益增长的需求，同时不影响性能。凭借弹性基础架构、动态资源分配和智能负载均衡，我们可以应对工作负载波动，同时保持效率和速度。
---
# 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://www.axisnow.io/zh/docs/security/service-reliability.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.