Alibaba Cloud Database · Open Source

Alibaba's MySQL branchwith DuckDB analyticsand native vector search

MySQL / InnoDB at the core, with DuckDB columnar analytics and native HNSW indexes.

Get started Explore the architecture

MySQL client / SQL

AliSQLMySQL service layer

InnoDBOLTP

Transactions · Vector search

HNSWNative flashback

DuckDBOLAP

Columnar analytics

Columnar storageVectorized execution

Latest feature releaseAliSQL 8.0.44-3MySQL 8.0.44 base GitHub6k+ Stars900+ Forks

LicenseGPL-2.0Public source and docs

Technology paths

Three core capabilities

A MySQL-compatible core, plus opt-in DuckDB analytics and native vector search.

Transactional kernel

MySQL 8.0-compatible kernel

Based on MySQL 8.0.44 and InnoDB, preserving familiar protocols, transactions, and row storage.

Explore MySQL / InnoDB

Columnar analytics

DuckDB analytical path

DuckDB provides columnar storage and vectorized execution for analytical tables and replicas.

Explore DuckDB

Native retrieval

Native HNSW indexes in InnoDB

InnoDB stores VECTOR data and HNSW indexes, queried through SQL with transaction visibility.

Explore vector search

Kernel extensions

Binlog in RedoEligible binlog events share InnoDB redo durability.

Native flashbackRead retained InnoDB history with AS OF TIMESTAMP.

SQL example

One MySQL entry point, three data paths

Use one MySQL connection for InnoDB, DuckDB, and Vector Index.

InnoDB runs directly; enable duckdb_mode or Vector Index for the other examples.

Full quick start

InnoDB transactions

CREATE TABLE orders (
  id BIGINT PRIMARY KEY,
  customer_id BIGINT NOT NULL,
  amount DECIMAL(18,2) NOT NULL,
  status VARCHAR(16) NOT NULL
) ENGINE=InnoDB;

START TRANSACTION;
INSERT INTO orders VALUES (1001, 42, 299.00, 'PAID');
SELECT id, amount, status FROM orders WHERE customer_id = 42;
COMMIT;