netpaladinx

10 ms·

1.
by netpaladinx 1y ago
I like the thread per core model. EloqKV, DragonflyDB, ScyllaDB all follow this pattern.
2.
by netpaladinx 1y ago
We’ve been using EloqKV to replace one of our largest Redis node (we didn’t want to run Redis Cluster, just a single big node). One pain point we had with Redis was the RDB fork causing latency jitter during persistence. EloqKV handles this
3.
by netpaladinx 1y ago
object storage here do you mean the recent released S3 Vector?
4.
Ursa: A leaderless, object storage–based alternative to Kafka(streamnative.io)
98 points by netpaladinx 1y ago|37 comments
5.
by netpaladinx 1y ago
Ursa published a blog post saying their leaderless, stateless, object storage–based Kafka replacement can reduce costs by up to 95%. Has anyone here tried Ursa in production? How much cost reduction have you actually seen compared to Kafka
6.
by netpaladinx 1y ago
All your points are valid. I don't think most people "dislike" C. People have options and most choose non-C. From my perspective, when the software or the system itself is already extremely complex, using C just adds more com
7.
by netpaladinx 1y ago
I remembered other Robotaxis operated one year ago
8.
by netpaladinx 1y ago
Which database is behind Claude Code? Cursor built on top of object storage. They failed with Yugabytes and Postgres
9.
by netpaladinx 2y ago
Talking about transactions in Redis, one area came on top of my head is metadata in file systems. I've seen colleagues/collaborators run large-scale training on a distributed file system w/ a billion files, which puts a lot o
10.
by netpaladinx 2y ago
Probably not. Data flow is declartive in data transformations and "differential" refers to be incremental. But what the link tries to model seems to relate to asynchronous transformations. Not on the same level.