Region limits
The available regions are China (Hangzhou) and China (Shanghai).
For information about feature releases and commercial availability, see the announcements on the official product website.
Billing limits
Only seven SOFAStack components are billed on a pay-as-you-go basis: Microservice Platform, Message Queue, Continuous Delivery, Data Access Proxy, Task Scheduling, API Gateway, and Real-time Monitoring Service (RMS). Other components are free to use. You are responsible for the costs of underlying resources, such as ECS, SLB, and OSS. To enable more components, go to the Component Center in the SOFAStack console and enable them as needed.
For more information about billing, see SOFAStack Pricing.
Quota limits
Limit Item | Limit for Regular Users | How to Request an Exception |
Number of workspaces | Depends on the number of available VPCs for the tenant. | Submit a ticket to request a VPC quota increase. |
Network environment | VPC network | None |
Application service technology stack | Technology Stack 2.0 | None |
Maven repository information for SOFABoot dependencies | Because the JAR packages are not in the Maven central repository, you must configure the endpoint and authentication information for the specified repository. | Submit a ticket to obtain the authentication information for the Maven repository. Then, update your local maven settings.xml file. |
Available product regions | China (Hangzhou), China (Shanghai) | None. See product update announcements. |
Available underlying resources (ECS, SLB, etc.) | The on-demand creation of underlying resources depends on the inventory in the corresponding zone. | Try selecting a different zone or confirm the resource inventory for the underlying resource in its console. |
Number of Kubernetes container clusters | There is a one-to-one relationship between workspaces and container clusters. | None |
Local access to the Kubernetes API Server | Access is limited to nodes or virtual machines within the VPC. | None |
Local access to the image repository within the containerized application service | Access is limited to nodes or virtual machines within the VPC. | None |
Pulling images from a third-party repository to a cluster | This depends on whether the ECS nodes have internet access or connectivity to the image repository. | Configure SNAT for the ECS nodes in the VPC to enable internet access. |
Serverless Application Service (SAS) cluster | SAS uses a unified shared cluster. The underlying resources are independent of the resources in your tenant account. | None. See product update announcements. |
Build and CI resources for continuous delivery | By default, a unified shared cluster is used. Performance may decrease as the number of tasks increases. You can register your own resources to ensure performance. | Submit a ticket to register your own build and CI resources. |