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

41–50 of 58 posts

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

#41

Post by zenmac »

ozgune wrote: post #37
baotiao wrote: post #29

Earlier quoted context omitted.

Here is the professional English translation of your analysis, optimized for a technical audience or a blog post: Why I Believe MySQL is More Suited than PostgreSQL for DuckDB Integration Currently, there are three mainstream solutions in the ecosystem: pg_duckdb, pg_mooncake, and pg_lake. However, they face several critical hurdles. First, PostgreSQL's logical replication is not mature enough—falling far behind the…

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

Thanks for providing this from PG perspective. Also wonder if storage engine such as OrioleDB would be better suited for FDWs to handle consistency between copies of the same data between DuckDB?

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

#42

Post by adsharma »

zenmac wrote: post #41
ozgune wrote: post #37

Earlier quoted context omitted.

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

Thanks for providing this from PG perspective. Also wonder if storage engine such as OrioleDB would be better suited for FDWs to handle consistency between copies of the same data between DuckDB?

The only concern I have about OrioleDB is how long it's taking to get to GA.

Anyone using it in prod even with the beta status?

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

#45

Post by manishsharan »

FoundationDB Record layer doesn't get much attention here but I have found that all my use cases are satisfied by it.

And I get the benefit of resiliency and DR for free.

If you are a developing for My SQL and you are using Java/kotlin/closure/scala consider this as well.

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

#46

Post by gempir »

rjh29 wrote: post #9
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.

Clickhouse supports MySQL protocol natively, and can also wrap/import MySQL tables. Okay so you need two connections but it works pretty well.

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

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

#47

Post by tempest_ »

gempir wrote: post #46
rjh29 wrote: post #9

Earlier quoted context omitted.

Clickhouse supports MySQL protocol natively, and can also wrap/import MySQL tables. Okay so you need two connections but it works pretty well.

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

Mostly due to support, at least on the PG side.

They bought peerdb and offer it as clickhouse pipes so I suspect the incentive to support that feature is pretty low

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

#48

Post by baotiao »

ozgune wrote: post #37
baotiao wrote: post #29

Earlier quoted context omitted.

Here is the professional English translation of your analysis, optimized for a technical audience or a blog post: Why I Believe MySQL is More Suited than PostgreSQL for DuckDB Integration Currently, there are three mainstream solutions in the ecosystem: pg_duckdb, pg_mooncake, and pg_lake. However, they face several critical hurdles. First, PostgreSQL's logical replication is not mature enough—falling far behind the…

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

Actually, that’s not the case. I also support PostgreSQL products in my professional work. However, specifically regarding this issue—as I mentioned in my article—it is simply easier to integrate DuckDB by leveraging MySQL's binlog and its pluggable storage engine architecture.
Post reply on HN