ApsaraDB for HBase:Integration overview

Version description

Alibaba Cloud APIs use version numbers to manage the API operations of ApsaraDB for Hbase clusters with different architectures. The following table describes the API version supported by ApsaraDB for HBase.

Online debugging

ApsaraDB for Hbase provides features such as API debugging in OpenAPI Explorer. Before you call API operations, you must understand the following information provided by ApsaraDB for Hbase: versions, endpoints, and integration methods.

API debugging URL

You can click the API debugging URL link to debug the API operations of ApsaraDB for Hbase.

Endpoint description

You can select an endpoint based on the region where your resource resides to reduce latency. For example, the virtual private cloud (VPC) endpoint of ApsaraDB for HBase in the China (Qingdao) region is hbase.aliyuncs.com.

• Public endpoints can be globally accessed.

• VPCs are isolated from each other. Each VPC corresponds to a virtual network. VPC endpoints have the following benefits:

  • Higher security: VPC endpoints are accessible only within the corresponding VPCs. This provides higher security and privacy.

  • Faster response: VPC endpoints use the internal network environment to deliver faster responses than public endpoints. In addition, you are free from issues such as network latency and bandwidth limits.

  • Lower cost: VPC endpoints are accessed over an internal network.

For more information, see Request structure.

Supported user identities

After you log on to OpenAPI Explorer by using your Alibaba Cloud account, OpenAPI Explorer uses your Alibaba Cloud account to perform online debugging by default. An Alibaba Cloud account has permissions on all API operations. Security risks may arise if you use an Alibaba Cloud account to debug API operations online. We recommend that you use a RAM user to call API operations or perform routine O&M. Before you call API operations as a RAM user, grant the required permissions to the RAM user based on your business requirements. Make sure that the RAM user has the management permissions on ApsaraDB for Hbase. For more information, see Customize a RAM policy.

Alibaba Cloud SDKs

• Alibaba Cloud provides SDKs in multiple programming languages, such as Java, C#, Go, Python, PHP, and C++. SDKs free you from considering the implementation details of API operations, and standardize the identity, authentication, and signing rules. You need to only integrate SDKs and use the SDKs to directly call API operations. For more information about Alibaba Cloud SDKs, see Alibaba Cloud SDKs.

• Alibaba Cloud SDKs can be used to call API operations of ApsaraDB for Hbase. For more information about the supported programming languages and dependency installation, see ApsaraDB for HBase.

Alibaba Cloud CLI

• Alibaba Cloud CLI allows you to use aliyun commands in the CLI shell to interact with Alibaba Cloud services and manage cloud service resources. For more information about Alibaba Cloud CLI, see What is Alibaba Cloud CLI?

• Alibaba Cloud CLI can be used to call API operations of ApsaraDB for Hbase. For more information, see the Call an RPC API section of the Call RPC API and RESTful API topic.

ROS

• ROS is an Alibaba Cloud service that can simplify the management of cloud computing resources. You can create templates to define the required Alibaba Cloud resources such as Elastic Compute Service (ECS) and ApsaraDB RDS instances, and dependency relationships between the resources. The ROS engine automatically creates and configures all resources in a stack based on a template to implement automated deployment and O&M. For more information, see What is ROS?

• ROS can be used to call API operations of ApsaraDB for Hbase. For more information about the resources and data sources supported by ROS, see Resources supported by ROS.

Custom encapsulation

You can encapsulate API requests based on your business requirements to call API operations. To make native HTTP calls, you must create custom requests and sign the requests. For more information about the signature mechanism, see Request syntax and signature method V3.