Help Center/ ServiceStage/ Service Overview/ Restrictions
Updated on 2024-05-09 GMT+08:00
View PDF
Share

Restrictions

ServiceStage has the following restrictions, and each of them applies to every tenant in any region.

Restriction is not resource quota limit. It indicates the maximum capabilities that ServiceStage can provide for tenants. Users need to pay attention to these restrictions when selecting technologies and designing solutions.

VM-based Deployment

When application components are deployed on VMs, ServiceStage manages a maximum of 5000 VM agents, and 1500 of them can directly communicate with ServiceStage without using VM environment proxies.

Registry and Discovery

For details about the restrictions on professional microservice engines, see Table 1.

Table 1 Restrictions on professional microservice engines

Item

Restrictions

Heartbeat reporting

Every 30s at most for every microservice instance

Service discovery

Every 30s at most for every microservice instance

Microservice instance registration

10 per second

For details about the restrictions on exclusive microservice engines, see Table 2.

Table 2 Restrictions on exclusive microservice engines (maximum specifications)

Item

Restrictions

Remarks

Heartbeat reporting

Every 20s at most for every microservice instance

Total rate limit: 2000 TPS

Service discovery

Every 20s at most for every microservice instance

-

Microservice instance registration

1000 per second

-

Exclusive Microservice Engine Types

An exclusive microservice engine of version 1.3.0 or later supports engine types listed in the following table. You can select an exclusive microservice engine of the required engine type.

Table 3 Exclusive microservice engine types

Engine Type

Application Scenario

AZ CPU Architecture

Cluster-deployed

Cluster-deployed engines support HA and host-level DR.

x86 or ARM. The hybrid architecture is not supported.

Requirements for Microservice Development Framework of a

The following table lists the recommended versions of the microservice development framework.

  • If you have used the microservice development framework of an earlier version to build applications, you are advised to upgrade it to the recommended version to obtain the stable and rich function experience.
  • If an application has been developed using the Spring Cloud microservice development framework, you are advised to use Spring Cloud Huawei to access the application.
  • If new microservice applications are developed based on open source and industry ecosystem components, you are advised to use the Spring Cloud framework.
  • If you want to use the out-of-the-box governance capability and high-performance RPC framework provided by microservice engines, you are advised to use the Java chassis framework.

Framework

Recommended Versions

Description

Spring Cloud Huawei

1.10.9-2021.0.x or later

Uses Spring Cloud Huawei for connection.

  • Spring Cloud version 2021.0.5
  • Spring Boot 2.6.13

Version description of the Spring Cloud microservice development framework: https://github.com/huaweicloud/spring-cloud-huawei/releases

Java Chassis

2.7.10 or later

Uses the software package provided by the open-source project for connection without introducing third-party software packages.

Version description of the Java chassis microservice development framework: https://github.com/apache/servicecomb-java-chassis/releases.

During system upgrade and reconstruction, third-party software conflict is the most common issue. Traditional software compatibility management policies do not adapt to software development for fast software iteration. In this case, see Third-Party Software Version Management Policy for version compatibility.

Exclusive Microservice Engine Quota

A quota refers to the maximum number of resources that you can create in an exclusive microservice engine instance. Table 4 provides the resource quota.

Table 4 Resource quota limits of microservice engines

Function

Resource

Quota

Modifiable

Precaution

Microservice management

Microservice versions

10,000

No

-

Data volume of a single instance (KB)

200

Yes

Increasing quotas prolongs the microservice discovery latency.

Number of contracts of a single microservice

500

No

-

Configuration management

Data volume of a single configuration item (KB)

128

No

-

Data volume of an application-level configuration

2,000

No

-

Microservice governance

Application-level governance policies

1,000

No

A maximum of 1000 governance policies are supported.
  • A single governance policy contains governance rules and service scenarios. Governance rules and service scenarios occupy the same quota in the configuration center.
  • Microservice version: In the microservice scenario, a version is used to mark the iteration record of a microservice to facilitate management of different iterations of a microservice.
  • Microservice instance: An instance is the minimum running and deployment unit of a microservice. Generally, it corresponds to an application process. A microservice can be deployed in multiple containers or VMs to enable multiple instances to run at the same time.
  • Configuration item: The configuration in the microservice scenario is to control the values of some variables in the program code. For example, dynamic configuration is to dynamically change the values of some variables during microservice running.