Based on our record, Minio seems to be a lot more popular than Hangfire. While we know about 155 links to Minio, 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.
> When it gets too out of hand, people will paper it over with a new, simpler abstraction layer, and the process starts again, only with a layer of garbage spaghetti underneath. I'm pretty happy that there are S3 compatible stores that you can host yourself, that aren't insanely complex. MinIO: https://min.io/ SeaweedFS: https://github.com/seaweedfs/seaweedfs Of course, many will prefer hosted/managed solutions... - Source: Hacker News / 6 days ago
Here are the basic steps to getting a minio tenant deployed inot kubernetes. There are some pre-requisites tasks to be deployed (and will not be covered in this article) including. - Source: dev.to / about 2 months ago
I'd throw minio [1] in the list there as well for homelab k8s object storage. [1] https://min.io/. - Source: Hacker News / 4 months ago
Can you just append the data to a blob using something like the s3 blob api? AWS, Azure and Minio https://min.io/ all support it. That way you don't have to reinvent the wheel. Source: 9 months ago
With that being said, you better take a look at something more WAN optimized and more secure, like S3 storage. You can build the S3 storage (and gain immutability) using something like MinIO (https://min.io/) or Ceph (https://ceph.io/en/) or check out Object First Ootbi offerings - https://objectfirst.com/object-storage/ (I work for them). Source: 10 months ago
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: almost 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
Ceph - Ceph is a distributed object store and file system designed to provide excellent performance...
Sidekiq - Sidekiq is a simple, efficient framework for background job processing in Ruby
Google Cloud Storage - Google Cloud Storage offers developers and IT organizations durable and highly available object storage.
RabbitMQ - RabbitMQ is an open source message broker software.
Azure Blob Storage - Use Azure Blob Storage to store all kinds of files. Azure hot, cool, and archive storage is reliable cloud object storage for unstructured data
Enqueue It - Easy and scalable solution for manage and execute background tasks seamlessly in .NET applications. It allows you to schedule, queue, and process your jobs and microservices efficiently.