What Is HTAP?

Overview

An HTAP instance can be used as a standby database of a GaussDB(for MySQL) instance and provides high-performance data analysis capabilities. Data is synchronized to the HTAP instance in real time. You can perform online transaction processing and online data analysis on your GaussDB(for MySQL) DB instance.

Supported Regions

HTAP instances are only available in the following regions:

• CN North-Beijing4
• CN East-Shanghai1
• CN South-Guangzhou
• AP-Singapore

Architecture

HTAP instances are deployed on ECSs and use extreme SSDs or ultra-high I/O disks.

You can enable binlog of your GaussDB(for MySQL) instance to synchronize data and operations to HTAP instances. The operations include inserting, deleting, modifying, and querying tables and changing table structures. After data is synchronized to an HTAP instance, you can access the HTAP instance through its private IP address and EIP for data analysis.

Figure 1 Architecture

Features

• Multi-Version Concurrency Control (MVCC) and transaction-level read consistency

  You can select required isolation levels among four isolation levels by configuring parameters in data synchronization task creation.

  • READ_UNCOMMITTED: Read operations are not committed, and transaction consistency cannot be ensured.
  • READ_COMMITTED: To ensure read consistency, read data is committed last.
  • QUERY_SNAPSHOT: Snapshot query can avoid data deduplication and merging, providing high query performance and ensuring read consistency.
  • QUERY_RAW: All raw data is returned, including data of different versions that have been deleted and updated.

• Quick deduplication

  Based on snapshots, data is quickly deduplicated to improve query performance.

• Data compression for storage

  In HTAP instances, data is compressed for storage by default, which greatly reduces storage costs under any given set of conditions.

• Parallel data synchronization

  In the initial full data synchronization phase, data is automatically sliced based on data statistics, and parallel processing improves synchronization performance. You can set the number of concurrent threads when creating a database for synchronization.

• Table definition rewriting

  When creating a synchronization task, you can modify tables to further improve the analysis and query performance. The modification operations include ORDER BY, PARTITION BY, SAMPLE BY, PRIMARY KEY, TTL and COLUMNS.

• Table filtering based on a blacklist and a whitelist

  When creating a synchronization task, you can select required tables or excluded tables based on a blacklist and a whitelist.

• Binlog

  When a database has multiple tasks for data synchronization, one binlog is used to reduce network resource consumption.

• Higher stability for data replication

  Most GaussDB(for MySQL) DDLs are supported for synchronization. The character set of the source database can be automatically converted to the UTF-8 character set of the destination database.

• Various data types

  All data types of GaussDB(for MySQL) are supported. For details, see Data Type Conversion.

• Aggregation of multiple data sources

  Data in multiple GaussDB(for MySQL) databases can be synchronized to the same HTAP instance.

• Enhanced security

  User account information is encrypted for storage.

Billing