This topic describes the functional limits of Blockchain as a Service.
General limits
Limit | Description |
|---|---|
Access to underlying cloud resources | To ensure the security and stability of Blockchain as a Service (BaaS), direct access to underlying cloud resources is not supported. These resources include ECS, Kubernetes clusters, Docker containers, Network-Attached Storage (NAS) file systems, and cloud disks. If you have related questions or requirements, submit a ticket for technical support. |
Hyperledger Fabric limits
Limit | Description |
|---|---|
Hyperledger Fabric version support | BaaS currently supports Hyperledger Fabric 2.2. For more information about the version support policy, see https://help.aliyun.com/document_detail/85759.html |
Blockchain ledger storage | Each BaaS product edition includes a NAS storage plan for the persistent storage of ledgers, data, and configurations. The cost of this plan is included in the price of the edition. If your storage usage exceeds the plan's capacity, the excess amount is billed on a pay-as-you-go basis for NAS. These charges are deducted from your account. |
CA cluster feature | The Certificate Authority (CA) dual-node cluster deployment feature for Hyperledger Fabric in BaaS is available only for the Enterprise Edition and Enterprise Security Edition. |
Customizing the number of Hyperledger Fabric nodes | BaaS for Hyperledger Fabric lets you dynamically add business organizations. By default, each organization has two peer nodes to ensure high availability. You cannot specify the number of peer nodes when you add an organization. The number of orderer nodes is three by default, and this number cannot be customized. |
Ledger data migration | BaaS for Hyperledger Fabric does not support directly importing existing blockchain ledger data. To migrate data, submit a ticket for Fabric migration to move your self-managed source Fabric to Alibaba Cloud Fabric. For more information, see Fabric Migration Issues. |
Hyperledger Fabric SDK management features | Management features of the Hyperledger Fabric SDK, such as creating channels, joining channels, and installing and instantiating chaincode, require administrator certificates of a business organization. For security reasons, BaaS does not directly provide these features. You can perform these operations in the BaaS console or by calling OpenAPI operations. For more information about BaaS APIs, see https://help.aliyun.com/document_detail/99197.html |
Chinese cryptographic algorithms | BaaS for Hyperledger Fabric supports the Chinese cryptographic algorithms SM2, SM3, and SM4. To ensure that all business organizations in the same consortium can perform encryption and decryption using these algorithms, all organizations must use deployment configurations that support them. To enable Chinese cryptographic algorithms, submit a ticket. The product team will then complete the required configurations. |
Reviewing chaincode source code | The BaaS console for Hyperledger Fabric does not support reviewing the source code of deployed chaincode. You can review the source code offline. |
Chaincode development | The BaaS console for Hyperledger Fabric does not provide an online development environment for chaincode. You can use VS Code to develop smart contracts and use VS Code to scan and deploy smart contracts. |
Interoperability | For a Fabric organization on Alibaba Cloud public cloud BaaS to interoperate with an external Fabric organization, specific version requirements must be met. If the consortium on BaaS is version 1.4, the external organization's Fabric version must be v1.4.2 or later, but earlier than v2.0. If the consortium on BaaS is version 2.2, the external organization's Fabric version must be 2.2.x. |