Overview
You can draw an overall architecture for an application. The service automatically calculates the SLO value of the architecture by analyzing how business units connect in series or parallel. You can quickly identify architecture weaknesses based on the calculated SLO value and adjust the number and layout of resource instances. You do not need to know the calculation details or worry about if there is any calculation error from data deviation or complex formulas.
In this module, you can manage application architectures. After you click an architecture name, you will be redirected to the page for drawing and governing architectures. On that page, you can draw an architecture and evaluate its SLO value.
Concepts
Service level objectives (SLOs) can be understood as the proportion of time that a system can provide services in the life cycle. Both availability and maintainability of the service need to be considered.
Service level indicators (SLIs) are specific metrics used to measure SLOs. They quantitatively measure a specific aspect of a service from the perspective of users. For example, if you have a website service, the SLI might be page loading time, request success rate, request delay, and traffic. If any indicator exceeds the normal range, the system is considered unable to provide services. The SLO value of the system decreases as the system fails to provide services for a longer time.
Service Level Agreements (SLAs) are formal, legally binding agreements between a service provider and its users, outlining the details of services, responsibilities and obligations of both parties, and liabilities for breach of these agreements. SLOs are typically included as part of quality standards in these agreements.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
