Apache ActiveMQ
RabbitMQ
IBM MQ
Apache Kafka
Amazon SQS
ChannelGrabber
Webgility
ZeroMQ
Hangfire
Sidekiq
Resque
Enqueue It
RabbitMQ
delayed_job
Apache Kafka
Amazon SQS
Apache ActiveMQ HangfireNo Apache ActiveMQ videos yet. You could help us improve this page by suggesting one.
Apache ActiveMQ might be a bit more popular than Hangfire. We know about 7 links to it since March 2021 and only 5 links to 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.
Before Kafka, traditional message queues like RabbitMQ and ActiveMQ were widely used, but they had limitations in handling massive, high-throughput real-time data streams. - Source: dev.to / 2 months ago
Consume open-source queuing services – customers can deploy message brokers such as ActiveMQ or RabbitMQ, to develop asynchronous applications, and when moving to the public cloud, use the cloud providers managed services alternatives. - Source: dev.to / 2 months ago
Apache ActiveMQ is an open-source Java-based message queue that can be accessed by clients written in Javascript, C, C++, Python and .NET. There are two versions of ActiveMQ, the existing “classic” version and the next generation “Artemis” version, which is currently being worked on. - Source: dev.to / almost 2 years ago
For real-time streaming, we have other frameworks and tools like Apache Kafka, ActiveMQ, and AWS Kinesis. - Source: dev.to / over 2 years ago
The back-end is designed as a set of microservices communicating through a message broker, ActiveMQ, with a custom configuration to support delayed delivery and other features. - Source: dev.to / almost 3 years 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 3 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 3 years ago
You can use hangfire for cronjob, to run at a time in future, you can use Hangfire.Schedule(jobid, datetime). Source: almost 3 years ago
So another option is to use something like https://hangfire.io to pull the jobs and process them? Source: about 3 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 4 years ago
RabbitMQ - RabbitMQ is an open source message broker software.
Sidekiq - Sidekiq is a simple, efficient framework for background job processing in Ruby
IBM MQ - IBM MQ is messaging middleware that simplifies and accelerates the integration of diverse applications and data across multiple platforms.
Resque - Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.
Apache Kafka - Apache Kafka is an open-source message broker project developed by the Apache Software Foundation written in Scala.
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.