Show HN: Ayder – HTTP-native durable event log written in C (curl as client)

Summary

Ayder HTTP-native durable event log / message bus — written in C A single-binary event streaming system where curl is your client. No JVM, no ZooKeeper, no thick client libraries. ▶️ 1-minute demo: SIGKILL → restart → data still there https://www.youtube.com/watch?v=c-n0X5t-A9Y # Produce curl -X POST ' localhost:1109/broker/topics/orders/produce ' \ -H ' Authorization: Bearer dev ' \ -d ' {"item":"widget"} ' # Consume curl ' localhost:1109/broker/consume/orders/mygroup/0?encoding=b64 ' \ -H ' Authorization: Bearer dev ' Why Ayder? Benchmark headline (3-node Raft, real network, sync-majority writes) Sustained: ~50K msg/s (wrk2 @ 50K req/s) (wrk2 @ 50K req/s) Client P99: 3.46ms Server P99.999: 1.22ms (handler only) (handler only) Recovery after SIGKILL: 40–50s (8M offsets) Kafka Redis Streams Ayder Protocol Binary (requires thick client) RESP HTTP (curl works) Durability ✅ Replicated log ⚠️ Async replication, no quorum ✅ Raft consensus (sync-majority) Operations ZooKeeper/KRaft + JVM tuning Single node or Redis Cluster Single binary, zero dependencies Latency (P99) 10-50ms N/A (async only) 3.5ms Recovery time 2+ hours (unclean shutdown) Minutes 40-50 seconds First message ~30 min setup ~5 min setup ~60 seconds Kafka is battle-tested but operationally heavy. JVM tuning, partition rebalancing, and config sprawl add up. Redis Streams is simple and fast, but replication is async-only — no majority quorum, no strong durability guarantees. Ayder sits in the middle: Kafka-grade durability (Raft sync-majority) with Redis-like simplicity (single binary, HTTP API). Think of it as what Nginx did to Apache — same pattern applied to event streaming. What You Get Append-only logs with per-partition offsets with per-partition offsets Consumer groups with committed offsets with committed offsets Durability via sealed append-only files (AOF) + crash recovery via sealed append-only files (AOF) + crash recovery HA replication with Raft consensus (3 / 5 / 7 node clusters) with Raft conse...