Aydarbek

8 ms·

1.
Temporal Shrinking(alperenkeles.com)
3 points by Aydarbek 3mo ago|1 comments
2.
Flatpak.org Rewrite(blog.jimmac.eu)
2 points by Aydarbek 3mo ago|0 comments
3.
How Long Does That Response Take for Real?(memcached.org)
2 points by Aydarbek 3mo ago|0 comments
4.
Linearizability and State-Machine Replication: Is It a Match?(arxiv.org)
1 points by Aydarbek 3mo ago|0 comments
5.
by Aydarbek 7mo ago
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 exposing the entire trail (proof JSON + docker inspect/
6.
Show HN: Ayder Crash Sandbox – SIGKILL durability proof (per-visitor container)(ayder.xyz)
1 points by Aydarbek 7mo ago|1 comments
7.
by Aydarbek 8mo ago
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, just early feedback and real workloads.
8.
Ask HN: Design partners wanted for a durable event log
1 points by Aydarbek 8mo ago|1 comments
9.
by Aydarbek 8mo ago
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 now doing short problem interviews with early users / pe
10.
by Aydarbek 8mo ago
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 hear what you’d do differently.
11.
Ask HN: How do you find a GTM cofounder for a developer-first infra startup?
3 points by Aydarbek 8mo ago|4 comments
12.
by Aydarbek 8mo ago
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 spec/libs it turns into bikeshedding. In Ayder the
13.
by Aydarbek 8mo ago
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 well. I kept the initial API explicit (`offset` / `limi
14.
by Aydarbek 8mo ago
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 the mental model I’d want: stable offsets, paging, resumabi
15.
by Aydarbek 8mo ago
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 consensus (Raft), real network (not loopback), and sync-majori
16.
by Aydarbek 8mo ago
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 iterate on wording and structure (including tooling), but the
17.
by Aydarbek 8mo ago
Thanks! If you hit any rough edges getting it running, tell me I’ll fix the docs/scripts.
18.
by Aydarbek 8mo ago
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 durability and recovery semantics nsq intentionally trades so
19.
by Aydarbek 8mo ago
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, and a very tight control over replication + execution order.
20.
by Aydarbek 8mo ago
The demo intentionally starts with SIGKILL to show crash recovery first. For benchmarks: I used real network (not loopback) and sync-majority writes in a 3-node Raft cluster. Happy to answer questions about tradeoffs vs Kafka / Redis S
21.
Show HN: Ayder – HTTP-native durable event log written in C (curl as client)(github.com)
56 points by Aydarbek 8mo ago|29 comments
22.
by Aydarbek 8mo ago
This is gold, thank you. The “easy to reason about” part is exactly what I’m going for. A couple quick questions if you don’t mind: Roughly what volume are you pushing per device (MB/day or events/sec), and what’s your typical off
23.
by Aydarbek 8mo ago
Disclosure: I built an OSS single-binary, HTTP-native durable event log aimed at this edge “store-and-forward + replay” problem. Repo: github.com/A1darbek/ayder If anyone is open to a tiny design-partner pilot (30–60 min): run doc
24.
Ask HN: How do you do store-and-forward telemetry at the edge?
8 points by Aydarbek 8mo ago|3 comments
25.
Show HN: Ayder – Nginx for event streaming (50K msg/s, P99 3ms, 40s recovery)(github.com)
4 points by Aydarbek 9mo ago|0 comments
26.
by Aydarbek 9mo ago
Author here. Happy to answer questions about the implementation. A few details that might interest HN: - Raft replication handles 50K msg/s with sync-majority writes - HTTP parsing is 0.4ms at P99.999 (picohttpparser, zero-copy) - Te
27.
Show HN: Ayder HTTP-native durable event log in C (50K msg/s, P99 3ms, Raft HA)(github.com)
2 points by Aydarbek 9mo ago|1 comments