Updated on 2025-11-21 GMT+08:00

Application Scenarios

Scientific Computing

Scientific computing in fields such as genomics and drug development requires high-performance and high-density computing. In addition, scientific computing is generally task-based and requires quick resource allocation and release. Therefore, a low-cost computing platform with automated O&M is required.

The following features make CCI suitable for scientific computing:

  • High-performance computing and network, and high I/O storage
  • Resource scaling in seconds, which minimizes resource consumption
  • No O&M required for clusters and servers, greatly reducing O&M costs
  • On-demand resource usage and pay-per-use billing
Figure 1 Scientific computing

DevOps

Software development enterprises need complete DevOps processes from code submission to application deployment to improve the development efficiency. DevOps processes such as continuous integration/continuous delivery (CI/CD) are generally task-based computing and require quick resource allocation and release.

The following features make CCI suitable for DevOps:

  • Automation for the entire CI/CD process, with no cluster creation and maintenance required
  • Image-based delivery for application data consistency between the development and production environments
  • On-demand resource usage and pay-per-use billing
Figure 2 DevOps

Services with Fluctuating Traffic

Some types of applications, such as applications for live streaming, media, e-commerce, and online education, have obvious traffic peaks and troughs. For these applications, resources need to be expanded rapidly during peak hours without breaking the bank.

The following features make CCI suitable for these applications:

  • Fast auto scaling: CCI can quickly take over services from CCE to ensure uptime during peak hours.
  • Low-cost, flexible billing: When services are stable, they can be run on CCE and be periodically billed. During peak hours, additional services can be run on CCI and be billed based on the usage. Resources are released after the traffic spikes, and the costs are greatly reduced.
Figure 3 Auto scaling