Using Quartz.net for background workers

[zbalkan]

Currently, apps work async and manage their background worker tasks with timers and tasks. It's likely to hit a concurrency tax f high number of parallel tasks managed by the same service.

Therefore, I suggest a background worker wrapper, preferably around Quartz, so that both the DNS server and the apps add the background worker jobs to the said worker queue. It decouples non-DNS tasks like background updates, log exporting, batch jobs, etc, from DNS server, keeping it lean and mean. It would also simplify developing apps as taks just need to be subscribed to the shared global background worker, and running them would be another component's concern.

[ShreyasZare]

Thanks for the post. This is something that is already implemented using custom task scheduler. So, the DNS resolver and the DNS server both use a separate task scheduler to avoid any such issues that may come due to too many tasks being generated.

[zbalkan]

But the apps do not make use of them, right? Is there a blocker for the apps to make use of the same scheduler?

[ShreyasZare]

The app methods that the DNS server calls are running on the task scheduler instance that the DNS server uses for answering queries.

Timer that some apps have would run on the .NET's default task scheduler which uses the shared thread pool that the runtime provides, which is fine since the timers are not very critical and short delays in execution are fine.

For specific apps that do logging, they are using Thread objects of their own since those task are long running for the entire duration.

[zbalkan]

Okay, so we are fine as is. Thanks.