Show HN: MainMemory – Wannabe Main Memory Database and More
1–4 of 4 posts
Re: Show HN: MainMemory – Wannabe Main Memory Database and More
#2i'm a bit confused about what this software is, at first form the description it seem a in memory database like redis or sqlite (with :memory ), but reading from the readme it seem more a framework for building server.
Can someone explain?
Re: Show HN: MainMemory – Wannabe Main Memory Database and More
#3i'm a bit confused about what this software is, at first form the description it seem a in memory database like redis or sqlite (with :memory ), but reading from the readme it seem more a framework for building server. Can someone explain?
At first I wanted to make an in-memory database. But I disliked libevent, libev and everything else I saw when I started it. Perhaps I would be more or less happy with libuv, but I was not aware of it back then. By the way redis also provides its own event handling machinery. I guess Salvatore did not like libevent too. But redis is single-threaded while my idea was to heavily rely on multi-threading and fibers (M:N threading model). Quite unexpectedly inventing a multi-threaded event handling framework with an added complexity of fibers took enormous time from me. Anyway now I have a cool framework for multi-threaded servers.
As for in-memory database functionality it only provides memcached compatible interface. As I'm done with the server framework stuff so I am going to add more features. Like persistance, basic redis protocol support, etc.
Re: Show HN: MainMemory – Wannabe Main Memory Database and More
#4i'm a bit confused about what this software is, at first form the description it seem a in memory database like redis or sqlite (with :memory ), but reading from the readme it seem more a framework for building server. Can someone explain?
At first I wanted to make an in-memory database. But I disliked libevent, libev and everything else I saw when I started it. Perhaps I would be more or less happy with libuv, but I was not aware of it back then. By the way redis also provides its own event handling machinery. I guess Salvatore did not like libevent too. But redis is single-threaded while my idea was to heavily rely on multi-threading and fibers (M:N…
ok, thanks for the explanation, it sound cool but you may want to update your readme! :)