Show HN: Duck – Making DuckDB feel like Swift
I was looking for a new database solution for my iOS and macOS apps. The original idea was pretty simple: bring the power O love about postgres onto the client side. I never liked CoreData. A long time ago I was using Realm because it solved my problem with slow batch insertions and brought reactivity. Nowadays there's SwiftData too, but I'm honestly not a fan of it at all. I'm in love with the server-side approach of working with SQL, like what I use with Vapor and what I originally built my Sw
Read original source
Source record
Recorded metrics
points · 3 votes
2026-11-13 01:17:02.887Z
cumulative since publication
Research analysis
Project record
Repository: swiftstream/Duck. Source account: I was looking for a new database solution for my iOS and macOS apps. The original idea was pretty simple: bring the power O love about postgres onto the client side. I never liked CoreData. A long time ago I was using Realm because it solved my problem with slow batch insertions and brought reactivity. Nowadays there's SwiftData too, but I'm honestly not a fan of it at all. I'm in love with the server-side approach of working with SQL, like what I use with Vapor and what I originally built my Sw
Observed adoption & comparisons
Source votes: 3 votes (Nov 13, 2026 UTC; cumulative since publication) Recent records to compare: “Show HN: Igloo – Self-hosted data warehouse built on DuckDB” (Show HN, Nov 11, 2026); “Show HN: TrueDate – Filter searches to pre-2023 and detect fake article dates” (Show HN, Nov 11, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.
Adoption decision
Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.
Unverified requirements
Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.
Next test
Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.