Current all interfaces for Job Service persistence are embedded in the application module. The goal is to refactor these interfaces and allow an abstraction of persistence that could have multiple implementations, with different modules.
It should be considered how persistence is chosen, current all implementation are embedded so the persistence is set with a configuration parameter during the startup, maybe we could change to some dependency based approach.