---
title: "Comment by Fabien M on \"Background processing in .NET Core: Quartz.NET\" | Hashnode"
description: "Hey Bogdan, Thanks for the nice articles! In the end did your team consider K8s CronJobs? For similar reasons to yours: db perf, I don't want to use Hangfir"
url: "https://hashnode.com/posts/background-processing-in-net-core-quartznet-1/614252a49c949972b85c7798/comment/614308e22d0e2479882a19a9"
---

[Discussion](https://hashnode.com/posts/background-processing-in-net-core-quartznet-1/614252a49c949972b85c7798)

Comment [Background processing in .NET Core: Quartz.NET](https://hashnode.com/posts/background-processing-in-net-core-quartznet-1/614252a49c949972b85c7798)

[Fabien M](https://hashnode.com/@fabienm)

[Sep 16, 2021](https://hashnode.com/posts/background-processing-in-net-core-quartznet-1/614252a49c949972b85c7798/comment/614308e22d0e2479882a19a9)

Hey Bogdan, Thanks for the nice articles! In the end did your team consider K8s CronJobs? For similar reasons to yours: db perf, I don't want to use Hangfire anymore, but also to keep the overall architecture simpler. Since we will anyway run in K8s, we consider using K8s CronJobs. The idea would be to call an HTTP endpoint, for ex: /jobs/doSomeLongRunningStuff Since it's not a good practice to have long running HTTP calls, it would simply enqueue a message. Later on, this would be dequeued and processed. Basically we trade the DB for the message queue.

[Bogdan Bujdea](https://hashnode.com/@bogdan)

[Sep 16, 2021](https://hashnode.com/posts/background-processing-in-net-core-quartznet-1/614252a49c949972b85c7798/comment/614308e22d0e2479882a19a9#reply-61432c83dbe60379639afc5c)

Hey Fabien! Yes, at the company where I worked with Hangfire, we replaced it with K8s CronJobs. Worked like a charm and I strongly advise to do the same :)