Hello everyone! ![]()
I am a Systems Engineering student. I’ve been studying high-performance backends and got tired of how standard message queues rely on heavy multi-threading and OS locks. So, to learn how things work under the hood, I decided to build my own from scratch in Rust.
It’s called Velocity-MQ.
My main goals were:
Thread-per-core architecture (Shared-nothing approach).
Zero-GC & Lock-Free: Built using atomic operations and Acquire/Release memory semantics instead of Mutexes.
io_uring: For asynchronous I/O to bypass standard epoll overhead.
Since I am a student and this is my first time implementing strict memory barriers (Acquire/Release) at this level, I would be incredibly grateful if senior Rustaceans could review my architecture and memory ordering. I want to make sure my lock-free structures are truly safe from subtle data races.
GitHub Repository:
I am open to all harsh architectural feedback, roasting, and PRs! Thank you so much for your time.
1 post - 1 participant
