nubskr

9 ms·

31.
by nubskr 11mo ago
They mostly play nicely together because they operate at different layers. Quinn's flow control handles transport level backpressure (receiver can't consume bytes fast enough), which naturally surfaces to OpenRaft as slower RPC re
32.
Octopii, a batteries included framework for building distributed systems in Rust(github.com)
5 points by nubskr 11mo ago|3 comments
33.
by nubskr 11mo ago
I recently open sourced Octopii, A batteries-included framework for building distributed systems, it bundles everything you need to build distributed systems without hunting for individual components.
34.
Walrus: A High Performance Storage Engine built from first principles
10 points by nubskr 1y ago|0 comments
35.
by nubskr 1y ago
try it out with: cargo add walrus-rust
36.
Walrus, A 1M ops/sec, 1 GB/s Write Ahead Log in Rust(nubskr.com)
4 points by nubskr 1y ago|1 comments
37.
by nubskr 2y ago
Working on a fast key value caching engine from scratch in golang with no dependencies https://github.com/nubskr/nubmq
38.
by nubskr 2y ago
have added a contributing md: https://github.com/nubskr/nubmq/blob/master/CONTRIBUTING.md feel free to open any issues :)
39.
by nubskr 2y ago
To put it bluntly—most engineers today confuse complexity with sophistication. They're stacking libraries and frameworks without questioning if that complexity is needed. nubmq rejects that entirely. It's built on the rawest form
40.
by nubskr 2y ago
Most 'built from scratch' projects still borrow heavily from established thinking—just reimplementing known patterns in different languages or flavors. But first principles means ripping out the assumptions entirely, starting with
41.
by nubskr 2y ago
Redis is single-threaded for dataset-modifying commands (SET, DEL, etc.), but multi-threaded for networking and I/O. nubmq, on the other hand, is fully multi-threaded—distributing reads and writes across all cores. So yes, this is fund
42.
by nubskr 2y ago
First principle? Don't respect traditions—burn them. No threads waiting on locks, no hard pauses for resizes, no conventional polling mechanisms. Instead, nubmq's entire architecture revolves around one relentless obsession: never
43.
by nubskr 2y ago
The benchmarks were done on an M2 MacBook Air (8-core) with 21M requests distributed across 100 concurrent clients sending requests as fast as possible(the test script is also in the github repo), a few reasons for being fast that come to m
44.
by nubskr 2y ago
It's still early, but it's been stress-tested pretty aggressively with high write loads and contention scenarios. Right now, it's feature-complete as a high-performance in-memory KV store with dynamic scaling. Clustering and
45.
by nubskr 2y ago
> *"The image here appears to be upside down (or rather rotated 180)"* Yeah, something weird happened with the image rendering; I'll fix that. > *"It's not clear from the readme physically where the data is st
46.
Nubmq: A high performant key-value store engine built from first principles
39 points by nubskr 2y ago|18 comments