Active?

[adamhathcock]

This looks interesting and a bit active. With the churn on dotnet 5 and be using a non-official hangfire storage, an EFCore solution would be better.

Does this work well? What issues do you have? I don't mind helping out on some outstanding work if there's any.

[sergezhigunov]

Yes, this is well tested and appears to be in some demand.
However, EFCore has several limitations that force you to choose for provider-specific implementations like Hangfire.SqlServer, Hangfire.PostgreSql and some others. For example, using optimistic concurrency when capturing a queue item is not as performant as when using an update query that returns output. There is a related issue #3.
Another issue #1 is that EFCore uses provider-specific migrations by design and it is quite problematic to create provider-neutral migrations.
And the next issue #2 is that most Hangfire queue implementations depend on Hangfire.SqlServer, where the queue service interface depends on TFM, which can lead to non-obvious consequences in complex dependency graphs.
I will be glad for any help or idea, if you have something. Thank you in advance.