Viewing profile — Aydarbek

[flagged]

[flagged]

[flagged]

Goal: make durability demos less “trust me”. Click “Run double proof” → it produces N, docker kill -s KILL, restarts, consumes/commits, then proves “no loss + no dupes” while expos…

Hi HN, Most durability demos are “trust me”: a blog post, a benchmark chart, or a unit test. This is a live sandbox that tries to make durability auditable. Every visitor gets: a d…

To clarify: I’m looking for 2–3 teams who already run Kafka/Redpanda/NATS and are open to testing an alternative focused on simpler ops and lower tail latency. Not selling anything…

Hi HN, I’m the author of a recent Show HN about a low-latency durable event log built directly on HTTP. I’m looking for 2–3 design partners to validate real-world needs around dura…

Thanks, this is genuinely helpful framing. We made the mistake of thinking in “roles” (GTM cofounder) instead of pulling people into the problem and watching for ownership. We’re n…

Happy to clarify: I’m not looking to hire or pitch just trying to understand how people here have successfully met cofounders in this space. If you’ve been through it, I’d love to …

I’m a solo technical founder building a curl-first, HTTP-native durable event log (Raft-based). A recent Show HN got ~90 GitHub stars and a few forks, which helped validate the tec…

That makes a lot of sense the hard part isn’t “HTTP paging”, it’s defining a safe cursor (in SQL that becomes “which column is actually stable/monotonic”), and without an external …

Yes, that maps quite naturally. Classic HTTP Range is byte-oriented, but custom range units (e.g. `Range: offsets=…`) or using `Link` headers for pagination both fit log semantics …

This resonates a lot. I’d love a world where “consume an event log” is a standard protocol and client-side tooling doesn’t care which broker is behind it. Feed API is very close to…

Totally fair, if this were “single-node HTTP handler on localhost”, then yeah, you can hit big numbers quickly in many stacks. The point of these numbers is the envelope: 3-node co…

Fair question. The benchmarks, logs, scripts, and recovery scenarios are all real and hand-run that’s the part I care most about being correct. For the README text itself: I did it…

Thanks! If you hit any rough edges getting it running, tell me I’ll fix the docs/scripts.

That’s a great comparison nsq is a project I have a lot of respect for. I think there’s a similar philosophy around simplicity and operator experience. Where Ayder diverges is in d…

Yes I’ve read through TigerBeetle’s VSR design and their rationale for not using Raft. VSR makes a lot of sense for their problem space: fixed schema, deterministic state machine, …