Nicheloom visits: 60,536 all-time · 7,913 in the last 7 days

The opportunity tracker for new startups.

Today: 895 launches · Niche of the day: browser-based video games · See what launched today →

Ducktape

a tiny HTTP/2 wrapper around DuckDB's Appender API

Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.

Want to reach these readers? Sponsor an issue.

Hi HN! I’m an engineer at Artie where we do real-time data replication.We were adding MotherDuck as a destination and the first version just used DuckDB’s Go driver directly. It worked great on my machine… until we wired it into our Transfer service (https://github.com/artie-labs/transfer).Because the driver requires CGO, our cross-compiles to amd64 and arm64 started failing, we lost our easy static binaries, and our Docker images had to pull in C toolchains and system libraries just to support one dependency. We tried isolating the CGO bits in a separate module, but it still caused CI failures and forced us to rewrite chunks of our build pipeline. At that point it was clear we didn’t want CGO anywhere near our main service.So I built ducktape: a tiny standalone microservice that wraps DuckDB’s Appender API behind HTTP/2 streams. Clients stream NDJSON over HTTP/2, and ducktape appends directly into DuckDB on the other side. No CGO in the main codebase, and we keep our cross-platform, pure-Go build story.The overhead was surprisingly low in benchmarks: ~757 MiB/sec over HTTP/2 vs ~848 MiB/sec in-process — about 90% of native performance but over the network.ducktape is open source and MIT licensed: https://github.com/artie-labs/ducktapeI’d love feedback, especially if you’ve tackled CGO isolation differently or have ideas to squeeze out more performance!

HN · launched Dec 16, 2025 · 12 upvotes (top 44%) · 0 views

Niche: network and communication protocol libraries · 71 launches, 5 in the last 7 days · Explore this niche →

Category and tags

  • Horizontal
  • Data infrastructure
  • Developer
  • Not AI
  • Hobby / open-source project

Visit website ↗ Source listing ↗

Could you build this?

No Building high-performance HTTP/2 streaming wrappers around DuckDB's internal C/C++ Appender API requires deep understanding of DuckDB internals, memory layouts, and low-level Go/C interop.

What it would actually take: This requires Go or C++ development wrapping the DuckDB C-API Appender directly via cgo without memory overhead, leveraging custom HTTP/2 or gRPC streaming protocols. It involves zero-copy data buffering, vector chunk serialization matching DuckDB's in-memory columnar format, and fine-grained mutex management for multi-threaded writes. Low-level database engine knowledge, memory layout tuning, and high-performance networking expertise are mandatory.

Discussion

No comments on this launch.

Competitors

Other products that read as similar to this one : 96 launches clear the similarity bar, closest 8 shown.

Attention rank: #37 of 97 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 48 days after the earliest competitor.

The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.