>>dzonga+3d
MariaDB has supported columnar tables for a bit https://mariadb.com/resources/blog/see-columnar-storage-for-...

>>dzonga+3d
Mariadb has a columnar engine already (though I did not use it myself) https://mariadb.com/docs/analytics/mariadb-columnstore/colum... and is mostly mysql compatible.

For about a year releases include a vector storage type, so it will be interesting to see it compared in performance with what Alibaba did.

Just wanted to plug that out. Given how often Postgres is plugged on HN, I think people ignore how versatile mariadb is.

>>baotia+(OP)
HTAP is here! It seems like these hybrid databases are slowly gaining adoption which is really cool to see.

The most interesting part of this is the improvements to transaction handling that it seems they've made in https://github.com/alibaba/AliSQL/blob/master/wiki/duckdb/du... (its also a good high level breakdown of MySQL internals too). Ensuring that the sync between the primary tables and the analytical ones are fast and most importantly, transactional, is awesome to see.

>>tempes+6l
in a way -- materialized views --

but Tiger Data is more optimized for TimeSeries data - https://www.tigerdata.com/docs/use-timescale/latest/hypercor...

I do wish too there was an embedded click house like db in Postgres

>>awesom+yw
I don't think MariaDB ColumnStore has any kind of advantage. It is just an append-only storage format with some columnar concepts.

https://vettabase.com/mariadb-columnstore-sql-limitations/#I...

>>ruhith+FE1
On this page, we introduce how to implement a read-only Columnar Store (DuckDB) node leveraging the MySQL binlog mechanism. https://github.com/alibaba/AliSQL/blob/master/wiki/duckdb/du... In this implementation, we have performed extensive optimizations for binlog batch transmission, write operations, and more.

>>baotia+(OP)
How easy will this be to combine with https://github.com/mysql/mysql-operator for deployment?

>>baotia+UV1
I feel this analysis is unfair to PostgreSQL. PG is highly extensible, allowing you to extend write-ahead logs, transaction subsystem, foreign data wrappers (FDW), indexes, types, replication, others.

I understand that MySQL follows a specific pluggable storage architecture. I also understand that the direct equivalent in PG appears to be table access methods (TAM). However, you don't need to use TAM to build this - I'd argue FDWs are much more suitable.

Also, I think this design assumes that you'd swap PG's storage engine and replicate data to DuckDB through logical replication. The explanation then notes deficiencies in PG's logical replication.

I don't think this is the only possible design. pg_lake provides a solid open source implementation on how else you could build this solution, if you're familiar with PG: https://github.com/Snowflake-Labs/pg_lake

All up, I feel this explanation is written from a MySQL-first perspective. "We built this valuable solution for MySQL. We're very familiar with MySQL's internals and we don't think those internals hold for PostgreSQL."

I agree with the solution's value and how it integrates with MySQL. I just think someone knowledgeable about PostgreSQL would have built things in a different way.

>>rjh29+Pu
It even supported running as a MySQL Replica at some point.

"MaterializedMySQL"

Sadly that feature seems to have been thrown out, probably due to complexity.

https://github.com/ClickHouse/ClickHouse/discussions/44887#d...

https://www.percona.com/blog/complete-walkthrough-mysql-to-c...

https://github.com/ClickHouse/ClickHouse/pull/73879

>>mhitza+6y
MariaDB also has MariaDB Exa, which is a real HTAP solution using Exasol for the analytical workloads: https://mariadb.com/products/exa/

>>jinjin+hq4
Also info here: https://www.exasol.com/use-cases/mariadb-exa/