Nicheloom visits: 58,301 all-time · 7,637 in the last 7 days

The opportunity tracker for new startups.

Today: 1,008 launches · Niche of the day: specialized calculation tools · See what launched today →

Ayder

HTTP-native durable event log written in C (curl as client)

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 built Ayder — a single-binary, HTTP-native durable event log written in C. The wedge is simple: curl is the client (no JVM, no ZooKeeper, no thick client libs).There’s a 2-minute demo that starts with an unclean SIGKILL, then restarts and verifies offsets + data are still there.Numbers (3-node Raft, real network, sync-majority writes, 64B payload): ~50K msg/s sustained (wrk2 @ 50K req/s), client P99 ~3.46ms. Crash recovery after SIGKILL is ~40–50s with ~8M offsets.Repo link has the video, benchmarks, and quick start. I’m looking for a few early design partners (any event ingestion/streaming workload).

HN · launched Jan 13, 2026 · 56 upvotes (top 18%) · 0 views

Niche: event streaming platforms · 38 launches, 2 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 ↗

More like this: all 38 launches in event streaming platforms →

Could you build this?

No Writing a durable, crash-consistent event log in C that survives SIGKILL with zero data corruption requires deep systems programming, storage engine design, and Linux kernel I/O expertise.

What it would actually take: The architecture requires low-level C with custom append-only segment storage, WAL, write barriers, fsync synchronization, memory mapping, and a custom epoll-based HTTP server. The core difficulty lies in crash recovery semantics, byte-level offset durability without external consensus engines, and extensive Jepsen-style fault injection testing.

Discussion

20 comments analyzed.

Competitors mentioned: Kafka, Feed API spec

Concerns raised: Performance comparable to quickly-written Python implementations, Poor quality software with bad performance (Kafka mentioned as established alternative), Overhead with indirection on cloud platforms like Digital Ocean, Scheduler overhead in userspace implementation, README feels like LLM-generated marketingspeak rather than authentic documentation

Feature requests: HTTP Range headers for offset-based pagination, Event log consumption as standardized protocol across brokers, Mature client libraries and external specification to avoid bikeshedding, Simpler Makefile using implicit C compilation rules

Competitors

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

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

Launched 76 days after the earliest competitor.

Related data

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.