Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adapter for Mnesia #29

Open
cabol opened this issue Oct 27, 2018 · 2 comments
Open

Adapter for Mnesia #29

cabol opened this issue Oct 27, 2018 · 2 comments

Comments

@cabol
Copy link
Owner

cabol commented Oct 27, 2018

The idea with this adapter is to provide another backend and be able to support different distributed topologies (replicated topology is a must).

@cabol cabol added the feature label Oct 27, 2018
@sheharyarn
Copy link

Was wondering if there has been any activity on this front? We recently felt the need for persistence in our cache layer and was wondering how easy would it be to get Mnesia working with Nebulex.

And thank you for the amazing package. I absolutely love Nebulex!

@cabol
Copy link
Owner Author

cabol commented Jan 24, 2020

Hey @sheharyarn, glad to hear that, thanks a lot :) !!

On the other hand, about the Mnesia adapter ...

Was wondering if there has been any activity on this front?

Right now it is kind of stuck, there have been other priorities, so a raw estimation to get it done could be 2-3 months. But this is on the top of the coming features for Nebulex along with the instrumentation via Telemetry.

We recently felt the need for persistence in our cache layer and was wondering how easy would it be to get Mnesia working with Nebulex.

I'd say it is easy, at least it shouldn't be that hard, there are a lot of examples of adapters that you can check and get a better idea. Also, I think this can be useful too: #51. It was the latest adapter, and within that issue history, you will find the suggestions, etc.

For me, the "hardest" part is the eviction algorithm, which is what defines a cache, e.g.: LRU, LFU, or the generational cache implemented by the local adapter. For the first draft, you can just skip that part and do something simpler, only implementing: Read-through and Read-through

So, if you want to implement it and contribute, it would be awesome, and I can help you with any questions or guidance you may need. Stay tuned!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants