Function Overview

This section describes how to use IAM to implement fine-grained permissions control for your ServiceStage resources. With IAM, you can:

• Create IAM users for employees based on the organizational structure of your enterprise. Each IAM user has their own security credentials for access to ServiceStage resources.
• Grant only the permissions required for users to perform a task.
• Entrust an account or cloud service to perform professional and efficient O&M on your ServiceStage resources.

An environment is a collection of basic compute (such as CCE and ECS), network (such as ELB and EIP), and middleware (such as DCS and RDS) resources, used for component deployment and running. ServiceStage combines multiple basic resources into an environment, including development, test, pre-production, and production environments.
Managing resources and deploying components by environment simplifies O&M management.
A maximum of 2000 environments can be created in a project.

An application is a service system with functions and consists of one or more components.
ServiceStage allows a single user to create a maximum of 7500 applications under the same project.

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.

After creating an application on ServiceStage, you can add components to the application. A maximum of 15,000 components can be created for an application.

You can set the component technology stack and component source based on service requirements to create and deploy components.

In ServiceStage, a configuration is a file. You can fill the environment and application system variables (such as the IP address, port number, database address, and application name associated with the environment) in a configuration file. When the component is associated with the configuration for deployment, the system variables are automatically replaced with the actual values. This implements multi-environment use with one-time configuration through file mounting.
A maximum of 1000 configuration files can be created in a project.

A release task provides functions for releasing applications: single-component release, batch operations (release, upgrade, and clone), and dependency-based orchestration. This feature enables you to flexibly deploy components in batches, improving service efficiency and user experience. 

• Create a batch deployment release task to deploy components of different technology stacks in different deployment environments of different applications.
• Create a batch upgrade release task to upgrade components of different applications in batches and specify the component upgrade sequence to ensure that services are not affected during the upgrade.
• Create a batch clone release task to clone components of different applications and quickly configure and deploy components in batches.

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.
Based on the built-in technology stacks, ServiceStage provides technology stack management to support technology stack version customization and multiple runtime systems.

Provides functions such as organization management, software repository, and image repository.

• Organization management is used to isolate images and assign access permissions (read, write, and manage) to different users.
• Image repositories are used to store and manage Docker images.
• Software repositories are used to store, manage, and deploy software packages.

Continuous delivery provides functions such as project build and release.

The microservice engine of ServiceStage supports access and governance of mainstream microservice frameworks. You can select a suitable microservice technology to quickly develop cloud applications to achieve complex and ever-changing service requirements.

• Supports the native ServiceComb microservice framework. Microservices developed by using the ServiceComb framework can be seamlessly connected to microservice engines. The microservice engine uses Apache ServiceComb Service Center, which is a RESTful-style, high-availability, and stateless service registry and discovery center and provides microservice discovery and management. Service providers can register their instance information with the registry and discovery center for users to discover and use.
• Compatible with mainstream microservice open-source frameworks. Provides a simple access mode for microservices developed by using Spring Cloud. You only need to modify the dependencies and configurations to access microservice engines and use the unified governance policies.
• Provides microservice governance. After an application developed using the microservice framework is managed on ServiceStage, the microservice will be registered with the service center after the application instance starts. You can govern microservices.