Help Center/ CodeArts/ Best Practices/ Developing an E-mall Project with CodeArts/ Resource Planning
Updated on 2025-07-30 GMT+08:00
View PDF
Share

Resource Planning

The required resources for this practice are listed in the table below. Prepare resources in the same region. This practice provides Cloud Container Engine (CCE) and Elastic Cloud Server (ECS) based deployment methods. Choose to prepare CCE or ECS resources to suite your needs.

Table 1 Resource planning

Service Name

Usage

Resource Description

Operation Guide

CodeArts

For E2E project R&D.
  • Package edition: Basic
  • Users: 5
  • Required duration: 1 month

Purchasing CodeArts

CCE

For deploying applications.

Cluster configuration: Select the pay-per-use billing mode.

  • Cluster type: CCE standard cluster
  • Cluster name: phoenix-cce
  • Cluster version: the latest version
  • Controller node architecture: x86
  • Network model: tunnel network
  • Container CIDR block: auto select

Buying a CCE Standard/Turbo Cluster

Node configuration: Select the pay-per-use billing mode.

  • Node type: Elastic Cloud Server (VM)
  • Specifications: 2 vCPUs | 8 GiB or above
  • Container engine: Docker
  • OS: Public image - EulerOS
  • Node IP: auto assign
  • EIP: auto create

Creating a Node

ECS

For deploying applications.

Select the pay-per-use billing mode.

  • CPU architecture: x86
  • Specifications: 2 vCPUs | 8 GiB or above
  • OS: Public image - Ubuntu 16.04
  • Elastic IP (EIP): billed by bandwidth, 5 Mbit/s
  • ECS Name: phoenix-ecs

After the purchase, add an inbound rule for the ECS's security group. Set the protocol to TCP, port to 5000-5001, and source address to 0.0.0.0/0.