Help Center/ ServiceStage/ User Guide/ Component Management/ Component Overview
Updated on 2025-08-12 GMT+08:00
View PDF
Share

Component Overview

Introduction

A component is a service feature implementation of an application. It is carried by code or software packages and can be independently deployed and run in an environment.

For details about applications and environments, see Application Overview and Environment Overview.

Figure 1 shows the relationships between components, applications, and environments.

Figure 1 Relationships

After creating an application and environment on ServiceStage, you can set the component technology stack and component source (package type and storage mode) based on service requirements to create and deploy components on the UI.

ServiceStage provides the capabilities of automatically creating and upgrading components using component templates. When creating a component using a component template, you can create configurations and Kubernetes resources. For details, see Creating a Component Using a Component Template.

Technology Stack

A technology stack includes the operating system, framework, and runtime system for component running. It consists of attributes such as the stack name, type, status, and version. The version complies with the semantic versioning specifications.

ServiceStage provides and manages the stack lifecycle. You only need to focus on service development to improve application hosting experience.

The lifecycle phases of the technology stack are defined as follows:

  • Preview: The beta version is released.
  • General Availability (GA): The official version is released.
  • End of Life (EOL): The lifecycle ends.

The technology stack status is defined as follows:

  • Preview: The stack is in the Preview phase.
  • Supported: The stack is in the GA phase.
  • Deprecated: The stack is in the GA phase but the EOL announcement has been released, or the stack is not recommended by ServiceStage.

Table 1 lists the open-source technology stacks provided by ServiceStage. If you encounter any problem when using the open-source technology stack, visit the official forum and community of the technology stack and contact technical support.

If these open-source technology stacks cannot meet your service requirements, you can use a custom technology stack. For details, see Adding a Custom Technology Stack Version.

ServiceStage supports the deployment of Java application components that are packaged as a WAR package and developed based on the Spring Boot framework. Version mapping between JDK and Spring Boot:

  • OpenJDK 8 supports Spring Boot 2.0.x to 2.7.x.
  • OpenJDK 11 supports Spring Boot 2.2.x to 2.7.x.
  • OpenJDK 17 supports Spring Boot 2.5.x and later.
  • OpenJDK 21 supports Spring Boot 2.7.x and later.

For details, see Spring Boot Versions.

Table 1 Open-source technology stack information

Technology Stack

Type

Status

Release Description

Package Type and Deployment Mode

OpenJDK8

Java

Supported
  • OpenJDK-8u442
  • Image OS: EulerOS 2.9.21. Character set en_US.UTF-8 is supported.

OpenJDK11

Java

Supported
  • OpenJDK 11.0.26
  • Image OS: EulerOS 2.9.21. Character set en_US.UTF-8 is supported.

OpenJDK17

Java

Supported
  • OpenJDK 17.0.14
  • Image OS: EulerOS 2.9.21. Character set en_US.UTF-8 is supported.

OpenJDK21

Java

Supported
  • OpenJDK 21.0.6
  • Image OS: EulerOS 2.9.21. Character set en_US.UTF-8 is supported.

Tomcat8/OpenJDK8

Tomcat

Supported

Tomcat9/OpenJDK8

Tomcat

Supported

Node.js8

Node.js

Supported

Node.js14

Node.js

Supported

Node.js16

Node.js

Supported

Node.js18

Node.js

Supported

If a component is created and deployed based on a VM using Node.js 18, the GLIBC version of the host OS in the component running environment must be 2.25 or later. Otherwise, the component cannot be started.

Docker

Docker

-

Supported by CCE. For details, see Kubernetes Release Notes.

The package type is image package and container-based deployment is supported. For details, see Component Deployment Modes.

Python3

Python

-

The package type is source code or ZIP package, and container-based deployment is supported. For details, see Component Deployment Modes.

Php7

Php

-

The package type is source code or ZIP package, and container-based deployment is supported. For details, see Component Deployment Modes.

Component Source

As shown in Table 1, when using ServiceStage to create and deploy a component, you need to select the component source based on the selected deployment mode. You can select source code repository, software package (JAR package, WAR package, ZIP package, or package), or image package. You can also select a package storage mode based on service requirements. For details, see Table 2.

Table 2 Component sources

Package Type

Storage Mode

Source Code Repository

Create authorization by referring to Creating Repository Authorization and set the code source.

JAR package

The following upload methods are supported:

  • Select the corresponding software package from the SWR software repository. Upload the software package to the software repository in advance. For details, see Uploading a Software Package.

    If PKIToken is disabled, the SWR repository is not supported.

  • Select the corresponding software package from OBS. Upload the software package to the OBS bucket in advance. For details, see Streaming Upload (PUT).
  • Obtain the corresponding software package from the custom file address. You can download the software package from the HTTP/HTTPS custom file address. Upload the software package to the corresponding custom file address in advance.

WAR package

ZIP package

Package

Image package

Containerized applications need to be created based on images. My Images (private images), Open Source Images, Shared Images, and Third-Party Images are supported.

  • If you select My Images, upload the image to the image repository in advance. For details, see Uploading an Image.
  • If you select Third-Party Images, ensure that you have obtained the address of the third-party image. The format of the image address is as follows: 
    {IP address of the third-party image repository}:{Port number for accessing the third-party image repository}/{Image storage path}/{Image name}:{Image tag}

    Alternatively:

    {Image name}:{Image tag}

    If the image tag is not specified, the latest version is used by default.

Component Deployment Modes

Table 3 describes the component deployment modes supported by ServiceStage.

Table 3 Deployment modes

Deployment Mode

Description

Container-based deployment

Uses container technologies (such as Docker and Kubernetes) to package applications and their dependencies, ensuring consistent running in any environment. This method effectively simplifies the deployment process and improves the consistency between development, test, and production environments. With CCE and custom Kubernetes clusters, you can easily deploy, manage, and scale containerized applications.

ServiceStage allows you to create and deploy components based on a container in a Kubernetes or VM + Kubernetes environment. For details, see Environment Type Description.

VM

A VM, or an ECS or custom server, is a basic computing unit that consists of vCPUs, memory, OS, and EVS disks. After creating an ECS, you can use it like using your local computer or physical server to deploy components.

ServiceStage allows you to create and deploy components based on a VM in a VM or VM + Kubernetes environment. For details, see Environment Type Description.

Component Management Process

Figure 2 Component management process

As shown in Figure 2, component management operations are as follows:

  1. Before using component management, you need to prepare the following resources:
    1. Upload the source code or software package of the component to be deployed to the repository based on Component Source.
    2. Create the environment to which the component to be deployed belongs based on Component Deployment Modes. For details, see Environment Management.
    3. Create the application to which the component to be deployed belongs. For details, see Application Management.
  2. Creating and Deploying a Component based on the Component Deployment Modes.
  3. Manage the created components:
Parent topic: Component Management