Durable Streams
Kafka-style semantics for client streaming over HTTP
Details
- External ID
- 46209189
- Source
- HN
- Company
- —
- Product
- Durable Streams
- Website domain
- github.com
- Launched
- Dec. 9, 2025
- Cohort
- —
- Upvotes
- 10
- Upvotes percentile
- 0.4933206106870229
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:25 p.m.
- Updated at
- Sept. 7, 2026, 9:25 p.m.
Description
Hey, I'm a co-founder at ElectricSQL. Durable Streams is the delivery protocol underneath our Postgres sync engine—we've been refining it in production for 18 months.The core idea: streams get their own URL and use opaque, monotonic offsets. Clients persist the last offset they processed and resume with "give me everything after X." No server-side session state, CDN-cacheable, plain HTTP.We kept seeing teams reinvent this for AI token streaming and real-time apps, so we're standardizing it as a standalone protocol.The repo has a reference Node.js server and TypeScript client. Would love to see implementations in other languages—there's a conformance test suite to validate compatibility.Happy to dig into the design tradeoffs—why plain HTTP over WebSockets, etc.
Enrichment
- Theme
- database infrastructure and developer tools
- Vertical
- Horizontal
- Function
- Data infrastructure
- Audience
- Developer
- AI stance
- Not AI
- Project type
- Commercial product
- Normalized one-liner
- kafka-style streaming for http clients
- Manually corrected
- False
Could you build this?
No Implementing durable HTTP streaming semantics with opaque monotonic offsets and distributed consensus is deep distributed systems engineering. It requires low-level network protocol design, high-performance WAL handling, and rock-solid fault tolerance.
What it would actually take: Requires an Elixir, Rust, or Go backend tailored for streaming and connection multiplexing, integrated with Postgres logical replication (WAL decoding). The system needs robust distributed storage for stream offsets, HTTP chunked transfer / Server-Sent Events handling with backpressure, and comprehensive correctness testing under network partitions.
Discussion
3 comments analyzed.
Competitors mentioned: Automerge, Loro, Yjs, CRDTs (Conflict-free Replicated Data Types)
Competitors
Other products that read as similar to this one — 67 launches clear the similarity bar, closest 8 shown.
Attention rank: #35 of 68 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 38 days after the earliest competitor.
- PicoMQ · hn · 2026-08-24 · 159 upvotes · similarity 0.51
- s2.dev: Streams as a cloud storage primitive · yc · 2025-11-08 · 63 upvotes · similarity 0.48
- StreamHouse · hn · 2026-02-25 · 10 upvotes · similarity 0.46
- Ayder · hn · 2026-01-13 · 56 upvotes · similarity 0.45
- RePlaya · hn · 2026-06-02 · 50 upvotes · similarity 0.45
- Streambed · hn · 2026-05-31 · 129 upvotes · similarity 0.42
- kassette · hn · 2026-07-13 · 9 upvotes · similarity 0.42
- UnisonDB · hn · 2025-11-01 · 17 upvotes · similarity 0.41
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a data infrastructure tool for Media & entertainment yet.