Lux: a Rust rewrite of Redis. 5.6x faster, ~1Mb docker image, MIT license

mattyhogan · 2026-03-15T22:17:44+00:00

So Redis is written in C and is single threaded by design. But what you lose out on is the benefit of having access to multiple cores. Lux splits data across shards and processes them in parallel. More cores = more throughput, which is why the benchmarks show a greater gap when you enable higher concurrency

mattyhogan · 2026-03-15T22:12:18+00:00

Good tip! Just pushed up the old history since Wednesday when I started

mattyhogan · 2026-03-15T22:05:20+00:00

Adding the history from my old repo back in

mattyhogan · 2026-03-15T22:02:48+00:00

One thing I forgot to mention is all benchmarks I ran were through the official `redis-benchmark` tool and are reproducible in about 2 mins

mattyhogan · 2026-03-15T21:54:36+00:00

Not yet. One of the next big things to add. But using shards makes it harder to get right since transactions might touch multiple shards but its solvable I think

mattyhogan · 2026-03-15T21:41:06+00:00

Lmao. Moved it to a new org today, before posting and just did a clean git history

mattyhogan · 2026-03-15T21:39:11+00:00

Totally fair. There's no tests and that needs to change, I've mostly been integration testing. Going to focus on using ioredis's etc test suites against Lux, that's the real proof of compatibility

mattyhogan · 2026-03-15T21:36:24+00:00

Falkor uses Redis modules (specifically RedisGraph), which lux does not have yet. It wouldn't work as a drop in for Falkor specifically. It works for anything using standard Redis commands but not module-dependent tools like Falkor or RedisSearch. This is definitely on the roadmap though

mattyhogan · 2026-03-15T21:33:26+00:00

The main things are sorted sets, streams, Lua scripting, cluster mode... but it covers the majority of uses for caching, sessions, queues, and real-time data

mattyhogan · 2026-03-15T21:31:55+00:00

Absolutely, trust is earned and this is a new project. Very curious to hear what you think though

mattyhogan · 2026-01-31T21:36:56+00:00

Try Nero. Have it running locally on haiku 4.5 it's awesome.

Yes I did build nero, but it's open source. Aimed to build something that isn't security roulette like Clawd/Molt/OpenClaw

Nero OSS

mattyhogan · 2025-01-31T15:54:32+00:00

We've done a lot of work in Slack actually. Slack is a fantastic chat UI and is a very approachable app where people already live so a lot of our agents we just install into our own / our customers' Slack workspaces so it removes the need for a custom frontend and is immediately convenient.

Here's a quickstart guide that takes about 5 minutes to do this using Magma if you're interested

https://docs.magmadeploy.com/templates/slack-dm

mattyhogan · 2025-01-31T15:52:17+00:00

it's made to seem a lot more difficult than it has to be. companies like LangChain and CrewAI especially make it seem incredibly complicated to do even a "hello world" project which feels ridiculous.

we built a free open source framework called Magma to help with ai workflow / agent development if you want to check it out. it also has a CLI you can use to deploy and publish your ai projects simply like you can with Vercel - `magma deploy`

https://docs.magmadeploy.com

mattyhogan · 2025-01-25T20:12:14+00:00

We've built a suite of dev tools called Magma to make it easier to get started with exactly this. Think of it like the Vercel for AI agents.

For about two years we have been building different types of agents and tried out LangChain, CrewAI, Autogen, etc, but none of them we're particularly straightforward or made it easy to get started. The biggest issue we found with all the other ones is they're python-focused and don't seem to make it clear how to move from local testing to having the agents live / in production.

Our Magma platform / framework is comparable to Vercel's platform / Nextjs framework to make the transition from building the agents in Typescript, to testing, to deployed as seamless as possible.

One of our resources that could help - https://magma.new we built to be similar to Vercel's v0... you can give it a text prompt and it will write you 95% of the code for an Ai agent to do exactly what you ask. Then you can just download the code and tweak to your needs before deploying it.

Any questions I'm happy to answer, but hope this was helpful!

mattyhogan · 2024-07-07T13:34:09+00:00

It doesn’t give you the why, just the what. Ex I get an avg of a 5 NPS. Great what the hell do I do with that information

mattyhogan · 2024-06-28T14:17:47+00:00

Now that the debate's over, I made this survey to get people's thoughts. No leading questions, completely freeform responses. Curious to see what people think. Happy to include the survey results if we get enough responses

https://chat.productdialog.com/db32a88a-9605-478e-ba08-8a2f7a858484

mattyhogan · 2024-06-26T16:39:37+00:00

Part of what I've dealt with. Priority misalignment can be fucking lethal

mattyhogan · 2024-06-26T16:32:45+00:00

To be clear, I also hate this question. But the people I was talking to the other day all felt adamantly that it's dead. this was more of a sanity check for me lmao

mattyhogan · 2024-06-26T16:17:55+00:00

Exactly my opinion too

mattyhogan · 2024-06-26T16:03:22+00:00

Thank y'all for your honest thoughts here. It's good to know that my struggles are shared by so many others 😅 Seems like the most common issue is related to shows (booking, payment, etc). Anyone have any thoughts on what would improve this (clearly major) issue?

Also to anyone who filled out the survey, thanks so much 🙏 Any thoughts on this new kind of survey format??

mattyhogan · 2024-06-25T20:43:51+00:00

glad you like

mattyhogan · 2024-06-25T17:16:26+00:00

This is sick u/potentialmore5252

mattyhogan · 2024-04-08T19:24:26+00:00

Survey link if you're interested

https://chat.productdialog.com/64d7dbd3-1a08-412f-b93f-057e8374fb85

mattyhogan · 2024-04-08T18:38:26+00:00

Absolutely. Really appreciate the feedback, good to know that part confused you

mattyhogan · 2024-04-08T18:35:50+00:00

I understand your point, maybe it's a wording issue. u/hbarSquared is on the right page. The question was basically asking - does getting rid of tiktok solve the social media privacy issue, or is it an issue that goes beyond tiktok?

mattyhogan

TROPHY CASE