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

Quartz.net #647

Closed
marll opened this issue May 6, 2022 · 1 comment
Closed

Quartz.net #647

marll opened this issue May 6, 2022 · 1 comment

Comments

@marll
Copy link

marll commented May 6, 2022

Hi,
it is possible to integrate the quart.net library?
Many thanks

@fretje
Copy link
Contributor

fretje commented May 6, 2022

Definitely possible... can be integrated into about anything dotnet...

Or are you talking about integrating it into the boilerplate itself out of the box?

That would be as an alternative to hangfire then... implemented as another IJobService... and then adding one or the other into DI according to the configuration. Could be a good exercise to adapt IJobService to be able to support multiple "providers"... as it's now 100% the same interface as hangfire. I think at least some changes will be needed there... would also need some extensive testing (which is still non existent as of now) to verify everything works across providers as it's supposed to...

Then there's also the "HangfireMediatorBridge" (#572). That's a proof of concept, but I'm successfully using it in my project... Planning to update the PR with my latest changes and adding some better examples once I find the time. That not only lets you very easily run any (mediatr) request as a backgroundtask, there's also the possibility to schedule "Recurring" jobs.
So that would then also have to be taken into account when working with Quartz instead... No small feat I think (but definitely not impossible ;-)).

I think the first thing which needs to be done in the template is actually add some more examples where the backgroundjobs are used (also recurring jobs) and then also add tests which verify they work as expected. Only then I would start thinking about implementing another provider.

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

No branches or pull requests

3 participants