NATS.io is a connective technology for distributed systems and is a perfect fit to connect devices, edge, cloud or hybrid deployments. True multi-tenancy makes NATS ideal for SaaS and self-healing and scaling technology allows for topology changes anytime with zero downtime.
Based on our record, NATS seems to be a lot more popular than Hangfire. While we know about 65 links to NATS, we've tracked only 5 mentions of Hangfire. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Hangfire (https://hangfire.io) includes default exception handling and is very extensible, I think it's a good mid-level choice and a good alternative to other queue mechanism, if you can't afford to host a separated queue service or can't manage a separated service; also scales pretty well (you can have multiple servers handling the same background job queue, or different queues). It runs on Sql Server and MySql... Source: almost 2 years ago
I used to just use hangfire.io in .net and worked wonderfully for any long running tasks or schedules. Had a great queuing system, UI to know if they failed , etc. That's how I'd send emails, pdf's, and other things along that nature. Then if it were more just a db related operation, just setup a schedule in mssql job service. Source: about 2 years ago
You can use hangfire for cronjob, to run at a time in future, you can use Hangfire.Schedule(jobid, datetime). Source: about 2 years ago
So another option is to use something like https://hangfire.io to pull the jobs and process them? Source: about 2 years ago
I've got a fairly large process I need to handle in background on my .net core web app so I've exported it to a background task using Hangfire. Source: almost 3 years ago
That sounds awesome. I have actually been working on something similar myself. I have been building a distributed NATS[0] cluster to funnel data down from the internet and index it locally. I also have a local Ollama box wired up to try to do some NLP on it. I started with Benthos to pull in, but since the recent license changes[1] I am rethinking that :( If you would like to collaborate feel free to shoot me an... - Source: Hacker News / 10 days ago
I've been happy with NATS, https://nats.io/. - Source: Hacker News / 14 days ago
Several message brokers, such as NATS and database queues, are not supported by OpenTelemetry (OTel) SDKs. This article will guide you on how to use context propagation explicitly with these message queues. - Source: dev.to / 2 months ago
Https://nats.io/ (Tracker removed) > Connective Technology for Adaptive Edge & Distributed Systems > An Introduction to NATS - The first screencast I guess I don't need to know what it is. - Source: Hacker News / 2 months ago
Pueue dumps the state of the queue to the disk as JSON every time the state changes, so when you have a lot of queued jobs this results in considerable disk io. I actually changed it to compress the state file via zstd which helped quite a bit but then eventually just moved on to running NATS [1] locally. [1] https://nats.io/. - Source: Hacker News / 3 months ago
Sidekiq - Sidekiq is a simple, efficient framework for background job processing in Ruby
Socket.io - Realtime application framework (Node.JS server)
Resque - Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.
Firebase - Firebase is a cloud service designed to power real-time, collaborative applications for mobile and web.
RabbitMQ - RabbitMQ is an open source message broker software.
Pusher - Pusher is a hosted API for quickly, easily and securely adding scalable realtime functionality via WebSockets to web and mobile apps.