Amazon SNS VS Hangfire

Amazon SNS Reviews

Hangfire Reviews

Amazon SNS mentions (54)

• Serverless Site Health Check Notification System

  This blog details how you can use some key serverless components from AWS like Amazon Eventbridge, AWS Lambda, and Simple Notification Service to setup a system that will monitor your site (which can be running anywhere) and send emails, text messages, slack messages, and more when the reachability status of your site changes. - Source: dev.to / 4 months ago

• WebSockets, gRPC, MQTT, and SSE - Which Real-Time Notification Method Is For You?

  Compare this to a stateless communication mechanism like Amazon SNS or other Webhook implementation where the connection is not persistent and the communication is one-way. These are intended to be used as a response to an event and inform subscribers without maintaining a continuous connection or keeping memory of previous interactions. - Source: dev.to / 6 months ago

• Programmatically reacting to S3 bucket external access exposures

  Let's make it simple and add an SNS topic target to the rule. We can add multiple different subscribers to the topic. Any time when Access Analyzer creates a new finding, SNS can, for example, send an email or a customized Slack message. - Source: dev.to / 8 months ago

• Receiving Slack notifications when CloudTrail logging gets turned off

  Of course, Slack is not the only way to receive notifications. EventBridge integrates with many target services, both AWS and 3rd parties. For example, we can set up email or phone text message alerts in SNS, or add a different target if business needs require. - 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: almost 3 years ago