Help Center/ Cloud Operations Center/ User Guide/ Resilience Center/ Architecture Design/ Creating a Deployment Architecture
Updated on 2026-06-23 GMT+08:00
View PDF
Share

Creating a Deployment Architecture

In the entire software development and O&M process, enterprises urgently need an intuitive and efficient architecture modeling and governance tool to efficiently manage and continuously optimize application architectures. However, traditional architecture management approaches often suffer from insufficient flexibility and lack of real-time visibility. As a result, the architecture information update is delayed, which directly undermines the efficiency and accuracy of architecture-related decisions.

To address these challenges, deploying a dedicated architecture tool enables real-time creation and dynamic updating of architecture data. After creating a deployment architecture, you can use this tool to perform operations in the entire architecture modeling and governance process. You can quickly sketch architecture diagrams aligned with your business applications using basic canvas elements such as border, node primitives, and edges. After saving, the complete architecture details become instantly available in the architecture governance module. This governance module not only visualizes the full architecture diagram but also displays key metrics such as the overall Service Level Objective (SLO) value. Additionally, it allows you to adjust application penalty-item configurations and automatically re-evaluates the aggregate SLO based on the updated settings, enabling dynamic calibration of architecture quality metrics.

By leveraging this deployment architecture tool, architectural information can be synchronized and accurately maintained in real time, ensuring the consistency between the architectural diagram and the actual business architecture. This fundamentally improves the efficiency, reliability, and scientific rigor of architectural decision-making.

Creating a Deployment Architecture

  1. Log in to COC.
  2. In the navigation pane, choose Resilience Center > Architecture Design. The Architecture Design page is displayed.
  3. Click Creating a Deployment Schema. The deployment architecture creation page is displayed on the right.
  4. On the deployment architecture creation page, set basic information about the deployment architecture by referring to Table 1.

    Figure 1 Setting basic architecture information

    Table 1 Basic information parameters

    Parameter

    Description

    Architecture Name

    Name of the deployment architecture

    The name must be unique and can contain a maximum of 128 characters, including letters, digits, hyphens (-), underscores (_), and spaces. It cannot start or end with a space.

    Architecture Description

    Description of the deployment architecture.

    Application

    Select the application to which the architecture belongs.

    After the architecture is created, its associated applications cannot be modified.

    Enterprise Project

    Select the enterprise project to which the deployment architecture belongs.

  5. After the basic information is configured, click OK.

    A message is displayed, indicating that the deployment architecture is created. In the deployment architecture list, you can view the created deployment architecture and go to the architecture details page to design an architecture and govern the architecture.

Drawing a Deployment Architecture

  1. On the displayed page, locate the target deployment architecture and click its name to go to its details page.
  2. Click Architecture Drawings to switch to the Architecture Drawings tab page.
  3. Sketch the architecture diagram as required.

    • Select an element in the left list and drag it into the canvas.
      Table 2 Element description of the canvas

      Element Type

      Description

      Example Value

      Border

      A border is used to wrap elements that need to be connected in parallel. You can double-click a border to configure the parallel relationship.

      Basic Diagram Elements > Border

      Element node

      An element node represents a specific cloud service. Each element node has an SLO value.

      Compute > Elastic Cloud Server

      Edge

      An edge represents a serial relationship between canvas elements. Only one edge can be dragged out to connect to another element on a canvas, and can be connected by only one edge.

      -
    • Drag an edge from one element to connect to another element in the canvas to establish a serial relationship between elements.
    • Drag a border from the diagram element list on the left to the canvas and use another element to establish a parallel relationship within it. An element can be a nested border or an element node.
    • Double-click the border to be connected in parallel and configure parameters on the displayed page.
      Table 3 Basic parameters

      Parameter

      Description

      Enable parallel configuration

      Whether to enable parallel configuration. If this parameter is enabled, the current border is enabled for parallel configuration.

      Redundancy mode

      Voting decision-making: In a K-out-of-N system, when N parallel nodes work at the same time, they share workloads evenly to ensure that at least K nodes are running normally. That is, the system can tolerate a maximum of N – K node failures. By default, K is set to 1, ensuring that at least one parallel node is running normally. In this case, the nodes are fully parallel, and the SLO availability calculation yields a probability of ≥ 1. For other values of K, the SLO availability calculation results in a probability of ≥ K.

      If the redundancy mode is set to voting decision-making, the following parameters need to be configured:

      • Number of votes (K): The redundancy mode of voting decision-making ensures that at least K parallel nodes are normal. The preset value is 1.
      • Number of active nodes: N parallel nodes that work at the same time in the redundancy mode of voting decision-making.

      N + M active/standby: N active nodes and M standby nodes. Only when one of the active nodes is faulty, the standby nodes start to work.

      If the redundancy mode is set to N + M active/standby, the following parameters need to be configured:

      • Number of active nodes: N active nodes in the redundancy mode of N + M active/standby.
      • Number of standby nodes: M standby nodes in the redundancy mode of N + M active/standby.
      • Active/standby mode: Active or standby nodes in the redundancy mode of N + M active/standby. An active or standby node can be an element node or border.

      N + 1 redundancy: N + 1 parallel nodes work at the same time and share even workloads. That is, at least N parallel nodes are normal, and the system can work properly only when there is no more than one faulty parallel node.

      If the redundancy mode is set to N + M active/standby, the following parameters need to be configured:

      Number of active nodes: N parallel nodes that work at the same time in N + 1 redundancy mode.

  4. Click Save.

Governing a Deployment Architecture

  1. Click Architecture Governance to switch to the Architecture Governance tab page.
  2. Click Deduction Item Configuration in the Architecture Governance tab page and configure the parameters on the displayed page.

    Figure 2 Configuring deduction items
    Table 4 Parameters for deduction item configuration

    Parameter

    Description

    Number of Planned Changes

    Number of plan changes within one year.

    Average change recovery duration (Minute)

    Average recovery duration of each change within one year, in minutes.

    Number of overload events

    Number of overload incidents that may occur within one year.

    Average recovery duration of overload incidents (Minute)

    Average recovery duration of each overload incident within one year, in minutes.

    Whether flow control measures are taken

    Whether to enable flow control. If this function is enabled, the settings of Number of overload events and Average recovery duration of overload events (Minute) become invalid.

    Number of other fault events

    Number of other fault incidents that may occur within one year.

    Mean Recovery Duration of Other Faults (Minute)

    Average recovery duration of other fault incidents within one year, in minutes.

  3. Click OK.

    After the deduction items are configured, the number of times that each type of incident occurs and the fault rectification duration increase. As a result, the SLO value decreases.

  4. Click Immediate assessment to re-evaluate the SLO value of the architecture.

    Figure 3 Evaluating the architecture diagram

Parent Topic: Architecture Design