Show HN: Lux – Drop-in Redis replacement in Rust. 5.6x faster, ~1MB Docker image

mattyhogan

I built Lux because Redis is single-threaded and hasn't changed architecturally since 2009. Lux uses a sharded concurrent architecture in Rust with per-shard reader-writer locks, zero-copy RESP parsing, and pipeline batching. It speaks RESP natively so every Redis client works unchanged. We benchmarked against Redis 7, Valkey 9, and KeyDB with redis-benchmark (50 clients, 1M requests) - full results in the README. The Docker image is ~1MB on ARM. MIT licensed, no plans to change that. If you don't want to self-host, there's managed hosting at luxdb.dev. Happy to answer questions about the architecture or benchmarks.

mholubowski

Why isn’t this getting any love? What’s the catch?

ArchieScrivener

Very cool. Clean.

japgolly

Good read here - https://www.luxdb.dev/architecture

kaoD

Discussion in Rust's subreddit, with some fair criticism: https://old.reddit.com/r/rust/comments/1ruq7tk/lux_a_rust_re... Some highlights that made me think: > It's easy to say you're faster if you don't actually support everything or maybe even made a mistake. > I don't see any tests so I wouldn't use this. --- > the repo has 5 commits and the first one is from 3 hours ago. "I've been working on" is probably more accurately "this morning I asked an ai to write this for me". --- > The single-threaded design of redis was specifically so that operations are ordered sequentially, so that the WAL-like log would be replayable and you'd get the exact same state as when shutting down the server. > Did you take any measures to ensure a sequential order of executed commands?

Bnjoroge

yeah a repo with only about 18 or so commits and about 3 days of commit history is definitely not vibecoded

gerdesj

There are six source files. No comments that I could see on a casual glance. It looks to me as vibed with post processing prompts enforcing minimalism. To be fair, this thing is a bare bones effort, ie v1 release to public. It looks like there is no config file and associated processing which might add a fair bit of code but that is probably an include and a stanza or two. If this is redis pared to the bone then it might actually fly. I suppose I ought to look at the source for redis to compare.

delduca

I bet it does not support Lua scripting.

delduca

What is the difference between your project and the linux fundation fork?

_pdp_

Typically you wait OSS projects to mature before you add a cloud offering but I guess not in the age of AI.

rvz

Sometimes, the test suite is a moat in open source and can be used to show you are a true 1:1 replacement with 100% compatibility, or with the test suite being closed source to protect against competing rewrites, just like with SQLite. So this isn’t a “drop-in Redis replacement”. It has no tests at all to verify 1:1 Redis functionality and of course it is fully AI generated. Avoid.

FergusArgyll

What's the future of Show HN? What do I as a reader do? just never look at it again? wait until it's used by a million people? Do I have to read the code of every new project posted here? I guess get codex to read it?!?!

bysiber

Curious about persistence - does this support RDB/AOF snapshots or is it purely in-memory? That's usually the first question that comes up when teams evaluate Redis alternatives.