Use scenarios

更新时间:
复制 MD 格式

Compute Nest helps service providers deliver, deploy, and maintain software services for their customers — without exposing customer infrastructure or exchanging credentials in plaintext. The following sections describe the two core use cases.

Automated application delivery and deployment

Deploying a modern application typically involves multiple interdependent cloud services — Virtual Private Cloud (VPC), Elastic Compute Service (ECS), ApsaraDB RDS, Server Load Balancer (SLB), ApsaraDB for Redis, and File Storage NAS (NAS) — along with environment setup steps such as configuring a Java Development Kit (JDK) and servers. Without automation, this work is error-prone and depends heavily on the knowledge of individual engineers. New technical support personnel must become familiar with the deployment procedure before making an attempt to deploy the service. Even minor mistakes, such as an invalid port or a version mismatch, can block deployment. Managing resources after deployment adds further complexity: checking cluster status, scaling in or out, and coordinating changes across multiple consoles.

The following diagram shows a typical manual deployment workflow.

Traditional model figure

Compute Nest automates the entire delivery pipeline. After Alibaba Cloud users subscribe to a service, Compute Nest provisions the required cloud resources and deploys the application automatically. This reduces both deployment time and the expertise required to operate the service. For a full list of benefits, see Benefits.

The following figure shows the flowchart of a traditional service deployment solution.

传统部署模式

Secure and auditable application O&M

Operations and maintenance (O&M) for customer-hosted deployments introduces security and accountability challenges: fault detection relies on customer feedback, and cross-platform troubleshooting can be time-consuming — leading to prolonged service interruption. Gaining access requires customers to share credentials in plaintext, opening and closing the O&M channel involves modifying network and security configurations, and there is no automatic audit trail when something goes wrong.

The following diagram shows a typical manual O&M workflow.

Traditional O&M service

The following figure shows the flowchart of the O&M process of a traditional enterprise application O&M solution.

传统代运维模式

Compute Nest replaces this process with a secure, audited channel:

  1. The customer grants access through Compute Nest — no plaintext credential exchange required.

  2. Compute Nest authenticates the connection automatically using its built-in authorization mechanism.

  3. The O&M session is recorded as logs and screen recordings, providing a complete audit trail for both parties to prevent disputes.

This approach eliminates the need to modify network and security configurations manually, and gives both you and your customers a verifiable record of every O&M operation. For a full list of benefits, see Benefits.