The DuckDB-based analytical primary instance is a cost-effective, lightweight solution for running complex analytical queries alongside your transactional workloads. This instance deeply integrates the DuckDB engine into the MySQL kernel, leveraging columnar storage and vectorized execution to deliver analytical query performance over 100x faster than the standard MySQL InnoDB engine. Additionally, its use of columnar storage significantly reduces storage costs through efficient compression. The instance fully retains the features of RDS for MySQL, ensuring seamless compatibility with the existing MySQL ecosystem and your workflows. You can operate this instance just like a regular RDS for MySQL instance, enjoying both robust transactional support and high-performance real-time analytics in a single solution. This empowers you to accelerate data-driven decision-making for your enterprise.
Core advantages
High-performance analytics: The built-in DuckDB engine supports features such as columnar storage, vectorized execution, efficient memory management, and parallel processing. These features improve complex query performance by over 100 times compared to standard MySQL.
Highly compatible with MySQL: The instance is fully compatible with the MySQL protocol, syntax, and data types. It supports transactions at the Snapshot Isolation level and uses MySQL binary logging (binlog) for data replication between primary and secondary instances to ensure data reliability and consistency.
Low storage cost: The columnar storage technology is used to provide a high data compression ratio. A DuckDB-based analytical primary instance uses over 50% less disk space than an instance that uses the InnoDB engine.
Secure and reliable: The instance uses a cluster architecture that supports automatic failover to ensure business continuity. The kernel is crash-safe to ensure data durability in extreme scenarios. The instance also supports a reliable backup and recovery mechanism that lets you perform a point-in-time restore.
Simple architecture: The instance uses the same database kernel as RDS for MySQL and has no external component dependencies.
For more information, see Technical principles.
Deployment models
Major engine version: MySQL 8.0.
Billing method: Pay-as-you-go and subscription.
Edition: Based on the RDS Cluster Edition architecture with one primary node and multiple secondary nodes. This architecture supports automatic failover. All secondary nodes are read-only. You can add or remove nodes as needed.
Storage type: Premium ESSD (storage capacity range: 20 GB to 128,000 GB).
Supported features
Category | Feature | Supported by DuckDB-based analytical primary instance |
Data migration | (Supported only when the DuckDB-based analytical primary instance is the destination) | |
Data synchronization | (Supported only when the DuckDB-based analytical primary instance is the destination) | |
Instance management | ||
(View-only) | ||
Restart a specified node | ||
Pause an instance | ||
Instance upgrade | ||
MySQL 8.0 is the latest major engine version that RDS for MySQL supports. You cannot upgrade to a later version. | ||
Account management | ||
Database management | ||
Database connection | ||
Monitoring and alerting | ||
Network management | ||
Read-only instances and read/write splitting | ||
Security management | ||
Manage sensitive data | ||
Auditing | ||
Database backup | ||
Configure a retention policy for backups after an instance is released | ||
Database recovery | ||
Diagnostics and optimization | ||
AliSQL | ||
Tag management | ||
Cluster node management | HA architecture with one primary node and multiple secondary nodes handling read requests | |