Cool!

I built CurioDB a while back with the same idea, but using Akka as the underlying framework. Persistent Redis with distributed transactions, embedded Lua and a websocket front-end:

https://github.com/stephenmcd/curiodb

You're not wrong, Walter.

A bug in a library like this is not a joke.

Sure, but OP didn't specifically ask you to review the code anyway, and there's a way to give feedback that doesn't make you look like an asshole.

> Sure, but OP didn't specifically ask you to review the code anyway,

Posting to Show HN isn't asking for review?

Right now all other feedback I am seeing is exactly like this:

https://xkcd.com/937/

CurioDB too: http://curiodb.jupo.org

I really love the idea of explaining the actor model as tons of tiny little servers compared to a single monolithic server. I tried to make the same comparison recently when I talked about adding distributed transactions to CurioDB (Redis clone built with Scala/Akka): http://blog.jupo.org/2016/01/28/distributed-transactions-in-...

What was the motivation to rebuild it in Scala?

If each key/value in the DB is treated as distributed (as per the actor model), a lot of the limitations Redis faces in a distributed environment are solved. I wrote a lot more about it here: http://blog.jupo.org/2015/07/08/curiodb-a-distributed-persis...

Great project. I recently used LuaJ to embed Lua scripting inside CurioDB: https://github.com/stephenmcd/curiodb - it's a distributed Redis clone built with Scala/Akka. In terms of matching features with Redis, LuaJ was a life-saver.

Yep, one actor per KV means some kind of distributed coordination would be needed - that doesn't exist yet.

Hey Jon, long time no see. :-)

Yes I imagine the thinking there is similar in your project, eg: Redis/CurioDB :: Node/SocketCluster (https://github.com/SocketCluster/socketcluster).

We should catch up sometime! I'd definitely like try out CurioDB at some point.

That'd be good!

Glad you like it!

Hardware requirements would depend on your usage of course, it's like asking about the length of a piece of string. :-)

Honestly though, the code probably needs a lot more eyeballs on it before it's production ready, which is why I posted it here.

It looks good, am sure there will be lots of folks to help on the project.

Ah yes that is true regarding the usage/req :), but I thought you might have tried it in production with some requirement.

Funny is a +1 on Slashdot, while on HN it'd be a -1.

Agreed. And that more than anything else about HN bothers me. I like intelligent humor. (Stupid humor however deserves to be down voted).

The rotated A in the Aerospike logo reminds me of a system that's fallen over, and now you can't unsee it:

http://www.aerospike.com/

Trying to read aerospike's front page to figure out what it is reminds me of this: http://shouldiuseacarousel.com/

"A system"? Not sure what you mean by that.

To me, it was immediately apparent that they are making the whole word Aerospike look like a rocket, a motif they repeat through their home-page.

Worker 1: "The server has fallen over."

Worker 2: "I'll go restart it."

See also: The frequent interchangeability of the words "system" and "computer".

My co-worker glanced at my screen and thought I was reading about erospike, which has a decidedly different feel, especially given the phallic imagery on the page.

Really? When I look at it I only see an eye (viewed in profile) with the legs of the A being eye lashes.