You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 16, 2020. It is now read-only.
I would like to implement mnesia support for toniq. Do you have any preference for how to add an extension point for a different backend? As far as I see redis communication is encapsultated inside of job_persistence.ex.
My plan is to change job_persistence so that it wraps a configurable backend module.
Regards
Ilja
The text was updated successfully, but these errors were encountered:
Sorry I didn't reply earlier. I don't actively work on this project, but I do aim to incorporate all contributions.
As you've seen I've tried to keep the redis usage as isolated as possible. Besides job_persistence.ex there is also keepalive_persistence.ex. You need to consider that one as well as it also deals with jobs.
I haven't put a lot of thought into how to support different backends. The two I can think of now is either making job_persistence have a backend (as you suggested), or making it the backend, like this?
Hi,
I would like to implement mnesia support for toniq. Do you have any preference for how to add an extension point for a different backend? As far as I see redis communication is encapsultated inside of job_persistence.ex.
My plan is to change job_persistence so that it wraps a configurable backend module.
Regards
Ilja
The text was updated successfully, but these errors were encountered: