If your business requires both high-concurrency online transaction processing (OLTP) and complex online analytical processing (OLAP), you can add DuckDB-based analytical read-only instances to your RDS for MySQL instance. This setup allows you to implement HTAP-based query routing through a database proxy. OLAP queries are routed to the DuckDB-based analytical read-only instances, while OLTP queries are routed to the primary RDS instance or regular read-only instances. This architecture enables enterprise users efficiently handle HTAP queries.
Effective date
October 14, 2025 (Singapore Time)
Introduction
The HTAP-based query routing solution for RDS for MySQL leverages the distinct advantages of different storage engines. A database proxy automatically directs requests to the most suitable instance type based on the estimated execution cost of SQL queries, achieving workload isolation and performance optimization.
Row-oriented instances: The primary RDS for MySQL instance and regular read-only instances use the InnoDB engine, which is ideal for handling high-concurrency OLTP read and write requests.
Columnstore instances: DuckDB-based analytical read-only instances use the DuckDB engine, which is designed for complex OLAP analytical queries.
Two routing methods are supported:
HTAP-based automatic query routing: Automatically routes OLAP and OLTP queries to columnstore or row-oriented instances based on the estimated SQL execution cost.
Manual routing by using hints: If automatic routing does not meet your expectations or your MySQL version does not support cost estimation, you can use hints to manually route SQL queries.
Usage notes
Before using HTAP-based automatic query routing, make sure that:
Your RDS instance runs MySQL 8.0 with a minor engine version of 20250731 or later, and has a DuckDB-based analytical read-only instance is created.
The database proxy feature is enabled, and the proxy version is 2.25.8 or later.
If your instnace's minor engine version or database proxy version does not meet the requirements, update the minor engine version or upgrade the database proxy version.
Billing
The HTAP-based automatic query routing feature is free of charge. You are charged only for the DuckDB-based analytical read-only instances that handles the OLAP queries. The fees on the buy page shall prevail.
Precautions
The latency threshold and consistency level of the database proxy also apply to the DuckDB-based read-only instances.
When you enable HTAP-based automatic query routing for a primary instance, theRead/Write Splitting Attribute of the instance's proxy endpoint must be set to Read/Write.
The read weights of DuckDB-based analytical read-only instances affect only the load balancing among these instances and do not influence the routing logic between row-oriented and columnstore instances.
If all DuckDB-based analytical read-only instances are at full capacity, subsequent analytical requests are queued for processing.
If you select Custom for Read Weight Allocation, the read weight of new DuckDB-based analytical read-only instance is set to 0 by default and must be configured manually.
You can configure the latency threshold, consistency level, read/write attribute, and read weight of database proxy based on your requirements. For more information, see Configure database proxy.