Help Center/ TaurusDB/ User Guide/ HTAP Analysis (Standard Edition)/ What Is HTAP Standard Edition?
Updated on 2025-08-21 GMT+08:00
View PDF
Share

What Is HTAP Standard Edition?

Hybrid Transactional and Analytical Processing (HTAP) is a data architecture that handles both online transactional processing (OLTP) and online analytical processing (OLAP) workloads.

It uses the column-based storage engine and Single Instruction Multiple Data (SIMD) for parallel compute. In massive data analysis scenarios, HTAP analysis provided by TaurusDB frees you from having to independently maintain data extraction and synchronization links. It reduces data management costs and provides simple and efficient real-time data analysis.

HTAP Standard Edition is developed based on open-source StarRocks.

Product Architecture

As shown in the following figure, there is an OLTP client and an OLAP client in an HTAP architecture. Data is synchronized through binlogs. OLAP instances are deployed on ECSs and use extreme SSDs or ultra-high I/O disks.

OLTP instances decouple storage from compute. Their data is shared and stored on shared storage. They use a row store format. This format allows you to quickly access all data of a record and is suitable for online transaction processing.

OLAP instances integrate storage and compute. Their data is stored on different disks. They use a column store format. This format allows you to quickly access the complete data of a column and is suitable for online analytical processing.

You can enable binlog for your TaurusDB instance to synchronize data and operations to OLAP instances. Synchronized operations include inserting table, deleting tables, and changing table structures. After data is synchronized to OLAP instances, you can access the instances using the private IP addresses or proxy addresses of the instances for data analysis.

Figure 1 Product architecture

A standard HTAP instance consists of frontend (FE) and backend (BE) nodes.

  • The FE nodes manage metadata, manage client connections, and plan and schedule queries. Each FE node stores and maintains a complete metadata backup in the memory to ensure data consistency between FE nodes. The FE nodes have three roles: fe-leader, fe-follower, and fe-observer.
    • The fe-leader nodes read and write metadata. The fe-follower and fe-observer nodes can only read metadata and route write requests for metadata to the fe-leader nodes. The fe-leader nodes update the metadata and synchronize the metadata changes to the fe-follower and fe-observer nodes.
    • The fe-follower nodes can only read metadata.
    • The fe-observer nodes synchronize and replay logs from the fe-leader nodes to update metadata. The fe-observer nodes are used to increase query concurrency of a cluster.
  • The BE nodes are for data storage and SQL computing.

Introduction Video

Main Features

  • Massively Parallel Processing (MPP) architecture

    Multiple nodes are used to execute queries in parallel.

  • High performance

    It supports vectorized engines and CBO optimizers and excels in queries for large and wide tables and multi-table join operations.

  • Standard SQL

    Query statements comply with the SQL-92 standard.

  • Data compression for storage

    Column-based storage and data compression greatly reduce your storage costs for any given set of conditions.

  • Aggregation of multiple data sources

    Data in multiple TaurusDB databases can be synchronized to a given HTAP instance.

Constraints

HTAP Standard Edition is only available in the following regions:

  • AP-Singapore
  • AF-Johannesburg

Billing

For details, see HTAP Instance Billed Items.

Parent Topic: HTAP Analysis (Standard Edition)