Amazon SQS VS Hangfire

Amazon SQS Reviews

Hangfire Reviews

Amazon SQS mentions (64)

• A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev

  SQS - 1 million messaging queue requests. - Source: dev.to / 3 months ago

• Building Mature Content Detection for Mod Tools

  The last stage is productionizing the model. The goal of this phase is to create a system to process each image/video, gather the relevant features and inputs to the models, integrate the models into a hosting service, and relay the corresponding model predictions to downstream consumers like the MCF system. We used an existing Safety service, Content Classification Service, to implement the aforementioned system... Source: 5 months ago

• Testing Serverless Applications on AWS

  For context; the web application is built with React and TypeScript which makes calls to an AppSync API that makes use of the Lambda and DynamoDB datasources. We use Step Functions to orchestrate the flow of events for complex processing like purchasing and renewing policies, and we use S3 and SQS to process document workloads. - Source: dev.to / 6 months ago

• The Role of Queues in Building Efficient Distributed Applications

  Amazon SQS is a fully managed message queue service that provides a reliable and scalable solution for asynchronous messaging between distributed components and microservices. - Source: dev.to / 9 months ago

• Debugging SQS subscription issues to topics

  The key service that publishes messages to its subscribers is Simple Notification Service (SNS). We can add multiple different subscribers to a topic, for example, email addresses, phone numbers, or SQS queues. - Source: dev.to / 10 months ago

Hangfire mentions (5)

• Do I need message queues for sending emails/texts via services like SendGrid, AWS SES, Twilio etc.? How do you decide if you need message queues or not? What questions do you ask yourself?

  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

• jsonb in postgres and should I use it or not?

  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

• How can In make a function run at a certain date in the future?

  You can use hangfire for cronjob, to run at a time in future, you can use Hangfire.Schedule(jobid, datetime). Source: almost 2 years ago

• How to handle processing of an entity through different states?

  So another option is to use something like https://hangfire.io to pull the jobs and process them? Source: about 2 years ago

• How to update database in a Parallel.For loop?

  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: over 2 years ago