Show HN: Skardi – SQL across Postgres, S3, and data lakes, served as a REST API

Posted by abbccdda on Tuesday April 14, 2026 @01:39PM
from the show-hn dept.

( 4 comments | 2 points | on HN )

Re:Show HN: Skardi – SQL across Postgres, S3, and data lakes... by durovilla on Tuesday April 14, 2026 @04:13PM (#47770852)

What are the main differences between this and DuckDB?

[ Parent | on HN ]

Re:Show HN: Skardi – SQL across Postgres, S3, and data lakes... by abbccdda on Tuesday April 14, 2026 @06:17PM (#47772189)

Hey there! The primary difference is that DuckDB is primarily a compute engine for analytical workloads, while Skardi is tackling the challenge with online serving queries. In addition, DuckDB provides read-only access to their data, while Skardi allows you to access multiple data sources and support read-write queries for a bunch of major stream DBs such as MySQL, Postgres, Mongo, etc.

Happy to list more comparisons if you want to discuss more!

[ Parent | on HN ]

Re:Show HN: Skardi – SQL across Postgres, S3, and data lakes... by zswen on Wednesday April 15, 2026 @01:05AM (#47774881)

How does Skardi compare to Presto for federated queries?

[ Parent | on HN ]

Re:Show HN: Skardi – SQL across Postgres, S3, and data lakes... by btnokami on Thursday April 16, 2026 @07:43AM (#47791646)

Hi, Also a contributor to skardi here. Presto is mainly focus on analytic queries, but skardi was optimized for serving online traffics, that means you can use skardi as a web server(define the SQL and skardi can turn it into a http server),I think that's the main difference.

[ Parent | on HN ]