This topic describes the benefits of ApsaraDB for HBase.
| Capability | ApsaraDB for HBase Performance-enhanced Edition (Lindorm) | Apache HBase | |
|---|---|---|---|
| Core features | HBase API | Supported | Supported |
| Data models | Supports multiple data models such as wide columns (HBase API), tables (SQL-like API), and queues. For more information about other data models, contact us. | Only the wide columns data model is supported. | |
| Global secondary index (GSI) | Provides built-in global secondary indexes. This helps make queries transparent, improves performance, and allows you to configure redundancy for non-index key columns as needed. For more information, see Secondary indexes. | Apache HBase requires external components to support global secondary indexes. In this case, the configuration process is complex. | |
| Full-text search | Intelligently integrates with the Apache Solr search engine. In this way, ApsaraDB for HBase Performance-enhanced Edition (Lindorm) provides a unified set of data access capabilities, such as storage, multi-dimensional queries, and full-text indexes of massive data. For more information, see Full-text index service. | Not supported | |
| Performance | Throughput | The throughput of an ApsaraDB for HBase Performance-enhanced Edition (Lindorm) instance is seven times that of an Apache HBase instance. For more information, see Test results. | No improvements. |
| Response latency | The P99 latency of an ApsaraDB for HBase Performance-enhanced Edition (Lindorm) instance is 1/10 of that of an Apache HBase instance. For more information, see Test results. | No improvements. | |
| Cost | Data compression | Provides a deeply optimized Zstandard (ZSTD) algorithm . Zstandard is rewritten by using JNA to eliminate core dumps. The algorithm is also optimized based on dictionary sampling. Therefore, the compression ratio of Zstandard is 50% higher than that of Snappy, and its data compression ratio can reach up to 10:1. | Apache HBase uses Snappy by default. If you use Zstandard, you must deploy a Hadoop-3.0 environment.Core dumps may occur. |
| Encoding | Supports the IndexableDelta algorithm. IndexableDelta provides the same compression ratio as the DIFF algorithm and an access speed twice that of using DIFF. | DIFF is used by default, which provides slower random access. | |
| Cold data and hot data separation | Automatically stores cold data and hot data in tiered storage. ApsaraDB for HBase Performance-enhanced Edition (Lindorm) uses high-compression and low-cost media to store cold data. This helps reduce the storage cost by 70% and improve the query performance for hot data by 15%. For more information, see Cold and hot data separation. | Not supported | |
| Storage medium | Supports ultra disks, standard SSDs, local HDDs, and local SSDs. ApsaraDB for HBase Performance-enhanced Edition (Lindorm) also supports Object Storage Service (OSS) that can be used to store cold data and capacity-optimized disks that are extremely cost-effective. Capacity-optimized disks will be available soon. | N/A | |
| Reliability | Active-standby redundancy | Supports advanced capabilities such as automatic failover and dual-cluster deployment for concurrent request processing. You can deploy an ApsaraDB for HBase Performance-enhanced Edition (Lindorm) instance and a self-managed Apache HBase instance in active/standby mode. | No improvements. Failover is not supported. |
| Backup and restoration | Allows you to back up more than 100 TB of data to Object Storage Service (OSS) and provides advanced capabilities such as a recovery time objective (RTO) of less than 30 minutes, on-demand backup, and point-in-time restoration. The RTO is ensured regardless of the data size. For more information, see Enable data backup and restoration. | Not supported | |
| MTTR | Has greatly improved the mean time to repair (MTTR). The fault recovery is 10 times as fast as that delivered by Apache HBase. | Not supported | |
| Multitenancy | Authentication and ACL | Allows you to authenticate users by username and password and manage permissions based on ACLs. For more information, see Manage users and ACLs. | The authentication process is complex. |
| Resource isolation | Provides the resource group feature to allow you to physically isolate resources among tenants. | Not supported | |
| O&M and diagnostics | O&M tools | Provides a GUI-based cluster management tool that allows you to manage tables, namespaces, groups, and ACLs. For more information, see Cluster management system. | HBase Shell |
| Data query | Supports HBase Shell and provides GUI-based SQL query in the cluster management system. For more information, see Data query. | HBase Shell | |
| Ecosystem | Data migration | Supports efficient, automated, and online data migration between HBase versions. The migration process does not affect your application and does not require modification of the application code. For more information, see Introduction to LTS (formerly known as BDS). | Only offline migration is supported. |
| Data synchronization from MySQL databases | Uses Lindorm Tunnel Service (LTS) to provide full data synchronization and real-time online data synchronization from MySQL databases to ApsaraDB for HBase. For more information, see Introduction to LTS (formerly known as BDS). | Apache HBase does not provide dedicated tools and does not support online incremental synchronization. You need to use third-party tools to migrate data from MySQL databases. | |
| Spark analysis | Deeply integrated with Apache Spark. For example, you can use Spark SQL to analyze data in ApsaraDB for HBase Performance-enhanced Edition (Lindorm), archive incremental data from ApsaraDB for HBase Performance-enhanced Edition (Lindorm) to Apache Spark, HDFS, or OSS, and return the analysis result that is generated offline to ApsaraDB for HBase Performance-enhanced Edition (Lindorm). | No improvements. Data integration requires heavy development workloads. | |
| MaxCompute | For more information, see Export full data to MaxCompute. | Data integration requires heavy development workloads. | |
| Log Service | Uses LTS to import incremental data from Log Service. For more information, see Introduction to LTS (formerly known as BDS). | Data integration requires heavy development workloads. | |
| Service capabilities | Service level agreement (SLA) | Provides SLA guarantees. ApsaraDB for HBase Performance-enhanced Edition (Lindorm) ensures up to 99.9% service availability for single-cluster deployment and 99.99% service availability for dual-cluster deployment. | N/A |
| O&M cost | Provides fully managed services. You do not need to invest in complex database O&M operations. | N/A | |
| Technical team | An expert team that consists of several Apache Project Management Committee (PMC) members and committers provides technical support. | N/A | |
| Practical experience | ApsaraDB for HBase Performance-enhanced Edition (Lindorm) is known for providing services in the previous nine years during the Tmall Double 11 Shopping Festival. Tens of thousands of ApsaraDB for HBase Performance-enhanced Edition (Lindorm) instances are deployed to support the business of Alibaba Group. | N/A | |