{"slug": "ducklake", "name": "DuckLake", "category": "databases", "category_name": "Databases", "description": "", "recommenders": 3, "commenters": 5, "warners": 0, "score": 3.499, "rising": 3.0, "first": "2026-05-12", "latest": "2026-10-27", "why": "Plus, it gives us a clear spec for implementing complex parts like time travel, snapshots, etc.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 2, "compare": 0, "warn": 0}, "spark": [0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 2], "listed": true, "loved": [], "caveat": "", "short_quote": "Plus, it gives us a clear spec for implementing complex parts like time travel, snapshots, etc.", "icon": true, "domain": null, "github_repo": null, "official_url": "https://ducklake.select", "pricing": "", "aliases": ["DuckLake", "Ducklake"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 800208705, "item_id": 50013044, "url": "https://news.ycombinator.com/item?id=50013044", "by": "eddietejeda", "date": "2026-10-08", "stance": "recommend", "quote": "Plus, it gives us a clear spec for implementing complex parts like time travel, snapshots, etc.", "excerpt": "Thanks for the shoutout. For context, we previously built custom catalogs optimized for specific use cases. But they were hard to maintain, especially as requirements changed, and Apache Iceberg was too heavy for our specific low-latency work. Since Ducklake is only a spec, we implemented datafusion-ducklake, and it performs as well as any custom or specialized catalog we built. We use Postgres as the catalog store, ", "context": "", "use_case": "data lake spec", "switched_from": "", "story": "DuckDB Ducklake"}, {"id": 800181184, "item_id": 50011324, "url": "https://news.ycombinator.com/item?id=50011324", "by": "smithclay", "date": "2026-10-08", "stance": "recommend", "quote": "it's just a (good) data lake spec that works in duckdb.", "excerpt": "Don't think it's widely known or understood, but Ducklake doesn't require duckdb: it's just a (good) data lake spec that works in duckdb. There's a cool alternate rust/datafusion ecosystem initiative going on at https://github.com/datafusion-contrib/datafusion-ducklake, and think the Quack protocol opens up a lot of cool possibilities too. If you need an idea for what do do with ducklake: recommend throwing all of yo", "context": "", "use_case": "data lake, agent traces", "switched_from": "", "story": "DuckDB Ducklake"}, {"id": 791240193, "item_id": 49452512, "url": "https://news.ycombinator.com/item?id=49452512", "by": "willbeddow", "date": "2026-08-26", "stance": "recommend", "quote": "we've adopted/extended it and ducklake very heavily at Krea for our research.", "excerpt": "This is a real shame. I love DuckDB, and we've adopted/extended it and ducklake very heavily at Krea for our research. I know the projects will remain open, and ostensibly still contributed to in the same direction, but surely AWS thinks of this as another piece of a product suite to compete with Databricks. Nontheless, I think the open embedded query engine approach DuckDB is spearheading is larger than one project,", "context": "works at Krea", "use_case": "research data lake", "switched_from": "", "story": "AWS Acquires DuckLabs"}]}], "caveats": [], "who": [{"by": "willbeddow", "context": "works at Krea", "url": "https://news.ycombinator.com/item?id=49452512", "date": "2026-08-26"}, {"by": "mritchie712", "context": "runs a lakehouse", "url": "https://news.ycombinator.com/item?id=48114417", "date": "2026-05-12"}], "tags": [], "use_cases": ["time series storage", "data lake spec", "data lake, agent traces", "research data lake", "lakehouse"], "compared": [{"slug": "postgresql", "name": "PostgreSQL", "co": 3, "switched_from": 0, "switched_to": 0}, {"slug": "duckdb", "name": "DuckDB", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=49996149", "title": "DuckDB Ducklake", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=50253890", "title": "Ask HN: How do you handle time-series metrics at scale without a large bill?", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49448321", "title": "AWS Acquires DuckLabs", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48111765", "title": "Quack: The DuckDB Client-Server Protocol", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {}, "2026-02": {}, "2026-03": {}, "2026-04": {}, "2026-05": {"neutral": 1}, "2026-06": {}, "2026-07": {}, "2026-08": {"recommend": 1}, "2026-09": {}, "2026-10": {"recommend": 2, "neutral": 1}}, "quotes": [{"id": 804079761, "item_id": 50254985, "url": "https://news.ycombinator.com/item?id=50254985", "by": "jauco", "date": "2026-10-27", "stance": "neutral", "quote": "", "excerpt": "We\u2019re on azure and a surprisingly good choice has been to use their eventhub to ingest the telemtry and then to consume it in batches of a few seconds using a consumer. Time series is hard because it is a lot of data that comes in all the time, this allows you to relax those requirements a bit. After eventhub we\u2019re using ducklake. But I\u2019m not at the point where I\u2019d flat out advise it to other people (just code immatu", "context": "", "use_case": "time series storage", "switched_from": "", "story": "Ask HN: How do you handle time-series metrics at scale without a large bill?"}, {"id": 800208705, "item_id": 50013044, "url": "https://news.ycombinator.com/item?id=50013044", "by": "eddietejeda", "date": "2026-10-08", "stance": "recommend", "quote": "Plus, it gives us a clear spec for implementing complex parts like time travel, snapshots, etc.", "excerpt": "Thanks for the shoutout. For context, we previously built custom catalogs optimized for specific use cases. But they were hard to maintain, especially as requirements changed, and Apache Iceberg was too heavy for our specific low-latency work. Since Ducklake is only a spec, we implemented datafusion-ducklake, and it performs as well as any custom or specialized catalog we built. We use Postgres as the catalog store, ", "context": "", "use_case": "data lake spec", "switched_from": "", "story": "DuckDB Ducklake"}, {"id": 800181184, "item_id": 50011324, "url": "https://news.ycombinator.com/item?id=50011324", "by": "smithclay", "date": "2026-10-08", "stance": "recommend", "quote": "it's just a (good) data lake spec that works in duckdb.", "excerpt": "Don't think it's widely known or understood, but Ducklake doesn't require duckdb: it's just a (good) data lake spec that works in duckdb. There's a cool alternate rust/datafusion ecosystem initiative going on at https://github.com/datafusion-contrib/datafusion-ducklake, and think the Quack protocol opens up a lot of cool possibilities too. If you need an idea for what do do with ducklake: recommend throwing all of yo", "context": "", "use_case": "data lake, agent traces", "switched_from": "", "story": "DuckDB Ducklake"}, {"id": 791240193, "item_id": 49452512, "url": "https://news.ycombinator.com/item?id=49452512", "by": "willbeddow", "date": "2026-08-26", "stance": "recommend", "quote": "we've adopted/extended it and ducklake very heavily at Krea for our research.", "excerpt": "This is a real shame. I love DuckDB, and we've adopted/extended it and ducklake very heavily at Krea for our research. I know the projects will remain open, and ostensibly still contributed to in the same direction, but surely AWS thinks of this as another piece of a product suite to compete with Databricks. Nontheless, I think the open embedded query engine approach DuckDB is spearheading is larger than one project,", "context": "works at Krea", "use_case": "research data lake", "switched_from": "", "story": "AWS Acquires DuckLabs"}, {"id": 769830672, "item_id": 48114417, "url": "https://news.ycombinator.com/item?id=48114417", "by": "mritchie712", "date": "2026-05-12", "stance": "neutral", "quote": "Our lakehouse uses ducklake with postgres as the catalog.", "excerpt": "> Can I use DuckDB with Quack as the catalog database for DuckLake? > Not yet, but we are working on it! Seems like a niche use case, but it's the one I'm most interested in. Our lakehouse uses ducklake with postgres as the catalog. Seems like a DuckDB / Quack catalog would be an excellent alternative.", "context": "runs a lakehouse", "use_case": "lakehouse", "switched_from": "", "story": "Quack: The DuckDB Client-Server Protocol"}]}