5 karma · joined May 30, 2022
Is there any plan? Is there any genuine problems? Like, you can simply change the setting to stop the auto changing of the brightness?
Also a lot of typos.
I hope it is useful for anyone who actually tries to use it, but more importantly, I would like to get feedback on the code and the implementation, possible improvement suggestions and more things I can add.
Thanks ahead for anyone checking it.
Your project looks very interesting as well.
My testing gave me really fast writes and deletes (since those are asynchronous), and reads were around 60 nanoseconds per read.
But it depends on the data type and I am planning to add more optimizations, especially with Rust NIFs anyways, so I will wait a bit before actually talking about the pure performance of the DB.
The name is like AlloyDB, yeah, but I use that "prefix" in most my projects so, not much I can do there, haha. :)
- Just learning more about databases while building a Redis alternative.
- It appends operations, the same ones you write to the TCP client and when loading them, just runs those one by one. I will still add some optimizations for e.g. repetitive commands.
- I haven't thought much about it yet, feel free to start a discussion in the GitHub repository to further talk about that.
- Probably not crash the server but return more useful errors and use Elixir's OTP features.
Glad to hear that you liked the project!
I am just handling the harder parts such as persistence by myself, to let the user only worry about writing features instead of reinventing the wheel.
Thanks!
I just set it to 12 GB max, since I have 32 GBs of RAM, and it works just great.
It has a better syntax, more up to date tools and is officially supported by JetBrains too. It also has the Ktor framework which is really fun to work with.