DistributedLock
QuartzNet
| DistributedLock | QuartzNet | |
|---|---|---|
| 5 | 30 | |
| 1,667 | 6,242 | |
| - | 1.1% | |
| 8.5 | 8.4 | |
| 26 days ago | 11 days ago | |
| C# | C# | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
DistributedLock
-
Ideas for concurrency control
You want a distributed lock then, maybe this project would help? https://github.com/madelson/DistributedLock
-
Distributed pool
Otherwise, you can probably look for libraries that do distributed locks (mutex or semaphore) like this one? https://github.com/madelson/DistributedLock
-
System Design Interview Question: Implementing a Scheduler
That’s it! The benefit of this approach is that the job does not depend on a particular framework or set of tools. It can be run as either a console application, or used in unit tests. What is most important to note is that concurrent jobs can affect subscriptions. So before sending a request to the payment gateway, always make sure that you have locked the resource. Every modern database supports distributed locks, and there are hundreds of frameworks on top of them. Examples of this can be found at https://github.com/madelson/DistributedLock. It is not a complicated task, but it is one that absolutely needs to be done.
-
How should I manage replicated backend service that has hosted background service
Seems like there are some solutions and libs out there like: Community made : https://github.com/madelson/DistributedLock Redis supported: https://github.com/samcook/RedLock.net
- What lock should I use to lock a User Object while be able to run methods async inside the lock?
QuartzNet
-
I open-sourced a lib for Message Queueing /w MongoDB - wise idea?
I would agree with using Job over Queue. Therefore I would recommend looking at Quartz.Net https://www.quartz-scheduler.net/
-
Sending recurring reminders through text message at user-defined times.
You can use something like https://www.quartz-scheduler.net/ to create multiple recurring jobs based on the definition you load from a DB.
-
Suggestions to scale this existing process
Or use an existing open source scheduling solution like https://www.quartz-scheduler.net/
- Hangfire - Schedule Background Jobs in ASP.NET Core
-
.NET Timer
If you're interested in using Quartz, you can check out their GitHub repo here: https://github.com/quartznet/quartznet. They also have extensive documentation available on their website: https://www.quartz-scheduler.net/documentation/index.html.
- How to do Recurring weekly events with timezones?
-
async await is doing problems in the background jobs(console scheduler app)
You should use an actual scheduler. https://www.quartz-scheduler.net/
- Is this the best way to have a thread manager?
- Scheduled job in dot ent
-
Will background threads be forced to exit in finally blocks once all main threads have exited
Better to use a framework like Quartz.NET for scheduling background tasks. How it works inside the box I have no idea, but I have used it extensively in my web applications, and those background tasks run 24/7, come hell or high water. It's a good library, and it's easy to use.
What are some alternatives?
RedLock.net - An implementation of the Redlock algorithm in C#
Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
AsyncEx - A helper library for async/await.
FluentScheduler - Automated job scheduler with fluent interface for the .NET platform.
Coravel - Near-zero config .NET library that makes advanced application features like Task Scheduling, Caching, Queuing, Event Broadcasting, and more a breeze!
aspnetcore-redis-rate-limiting - Set up a Redis backplane for ASP.NET Core multi-node deployments, using the built-in Rate Limiting support that's part of .NET 7 and .NET 8.
Cronos - A fully-featured .NET library for working with Cron expressions. Built with time zones in mind and intuitively handles daylight saving time transitions
Workflow Core - Lightweight workflow engine for .NET Standard
NCrontab - Crontab for .NET
DurableTask - Durable Task Framework allows users to write long running persistent workflows in C# using the async/await capabilities.
Chroniton - A library for running tasks(jobs) on schedules.