Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AliSQL: Alibaba's open-source MySQL with vector and DuckDB engines

github.com

Post reply on HN
Print view View original

51–58 of 58 posts

Re: AliSQL: Alibaba's open-source MySQL with vector and DuckDB engines

#51

Post by jinjin2 »

mhitza wrote: post #11
dzonga wrote: post #5

having an embedded column database for analytics in your traditional db is a massive win for productivity + operations simplicity. at the moment I use PG + Tiger Data - couldn't find a mysql equivalent so this as one.

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 mari…

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

Re: AliSQL: Alibaba's open-source MySQL with vector and DuckDB engines

#52

Post by infogulch »

How I see SQL databases evolving over the next 10 years:

    1. integrate an off the shelf OLAP engine
       forward OLAP queries to it
       deal with continued issues keeping the two datasets in sync
    2. rebase OLTP and OLAP engines to use a unified storage layer
       storage layer supports both page-aligned row-oriented files and column-oriented files and remote files
       still have data and semantic inconsistencies due to running two engines
    3. merge the engines
       policy to automatically archive old records to a compressed column-oriented file format
       option to move archived record files to remote object storage, fetch on demand
       queries seamlessly integrate data from freshly updated records and archived records
       only noticeable difference is queries for very old records seem to take a few seconds longer to get the results back

Re: AliSQL: Alibaba's open-source MySQL with vector and DuckDB engines

#53

Post by redwood »

baotiao wrote: post #50
redwood wrote: post #43

Wonder how DuckDB compares here to what TiDB did using Clickhouse instead

I’m quite certain that if DuckDB had been open-sourced and reached stability around 2020, TiDB would have definitely chosen DuckDB instead of ClickHouse.

Interesting. I'd think they serve different purposes

Re: AliSQL: Alibaba's open-source MySQL with vector and DuckDB engines

#55

Post by geab »

jinjin2 wrote: post #51
mhitza wrote: post #11

Earlier quoted context omitted.

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 mari…

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

Also info here: https://www.exasol.com/use-cases/mariadb-exa/

Re: AliSQL: Alibaba's open-source MySQL with vector and DuckDB engines

#57

Post by baotiao »

polskibus wrote: post #16

Does this feed DuckDb continuously data from transactional workloads, akin to what SAP hana does? If so that would be huge - people spend lots of time trying to stitch transactional data to warehouses using Kafka/debezium. BTW, Would be great to hear apavlo’s opinion on this.

Yes, MySQL-DuckDB columned read only node will continuously get data from transactional workload by binlog. Then people will not need to maintain tools like kafka/debezium to sync between two node.

Re: AliSQL: Alibaba's open-source MySQL with vector and DuckDB engines

#58

Post by anentropic »

baotiao wrote: post #49
anentropic wrote: post #32

How easy will this be to combine with https://github.com/mysql/mysql-operator for deployment?

We havn't try that before, maybe I will try to combine with mysql-operator later..

Or just any guidance on production deployments would be appreciated
Post reply on HN