Alternatives to Hangfire logo

Alternatives to Hangfire

RabbitMQ, NServiceBus, Azure Functions, Kafka, and Sidekiq are the most popular alternatives and competitors to Hangfire.
96
108
+ 1
13

What is Hangfire and what are its top alternatives?

It is an open-source framework that helps you to create, process and manage your background jobs, i.e. operations you don't want to put in your request processing pipeline. It supports all kind of background tasks – short-running and long-running, CPU intensive and I/O intensive, one shot and recurrent.
Hangfire is a tool in the Background Processing category of a tech stack.
Hangfire is an open source tool with 6.5K GitHub stars and 1.4K GitHub forks. Here’s a link to Hangfire's open source repository on GitHub

Top Alternatives to Hangfire

  • RabbitMQ

    RabbitMQ

    RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received. ...

  • NServiceBus

    NServiceBus

    Performance, scalability, pub/sub, reliable integration, workflow orchestration, and everything else you could possibly want in a service bus. ...

  • Azure Functions

    Azure Functions

    Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems. ...

  • Kafka

    Kafka

    Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design. ...

  • Sidekiq

    Sidekiq

    Sidekiq uses threads to handle many jobs at the same time in the same process. It does not require Rails but will integrate tightly with Rails 3/4 to make background processing dead simple. ...

  • Resque

    Resque

    Background jobs can be any Ruby class or module that responds to perform. Your existing classes can easily be converted to background jobs or you can create new classes specifically to do work. Or, you can do both. ...

  • Beanstalkd

    Beanstalkd

    Beanstalks's interface is generic, but was originally designed for reducing the latency of page views in high-volume web applications by running time-consuming tasks asynchronously. ...

  • PHP-FPM

    PHP-FPM

    It is an alternative PHP FastCGI implementation with some additional features useful for sites of any size, especially busier sites. It includes Adaptive process spawning, Advanced process management with graceful stop/start, Emergency restart in case of accidental opcode cache destruction etc. ...

Hangfire alternatives & related posts

RabbitMQ logo

RabbitMQ

12.3K
10.4K
507
Open source multiprotocol messaging broker
12.3K
10.4K
+ 1
507
PROS OF RABBITMQ
  • 225
    It's fast and it works with good metrics/monitoring
  • 78
    Ease of configuration
  • 56
    I like the admin interface
  • 49
    Easy to set-up and start with
  • 20
    Durable
  • 18
    Standard protocols
  • 18
    Intuitive work through python
  • 10
    Written primarily in Erlang
  • 7
    Simply superb
  • 6
    Completeness of messaging patterns
  • 3
    Scales to 1 million messages per second
  • 3
    Reliable
  • 2
    Better than most traditional queue based message broker
  • 2
    Distributed
  • 2
    Supports AMQP
  • 1
    Great ui
  • 1
    Better routing system
  • 1
    Inubit Integration
  • 1
    Reliability
  • 1
    High performance
  • 1
    Runs on Open Telecom Platform
  • 1
    Clusterable
  • 1
    Clear documentation with different scripting language
CONS OF RABBITMQ
  • 9
    Too complicated cluster/HA config and management
  • 6
    Needs Erlang runtime. Need ops good with Erlang runtime
  • 5
    Configuration must be done first, not by your code
  • 4
    Slow

related RabbitMQ posts

James Cunningham
Operations Engineer at Sentry · | 18 upvotes · 1.1M views
Shared insights
on
CeleryCeleryRabbitMQRabbitMQ
at

As Sentry runs throughout the day, there are about 50 different offline tasks that we execute—anything from “process this event, pretty please” to “send all of these cool people some emails.” There are some that we execute once a day and some that execute thousands per second.

Managing this variety requires a reliably high-throughput message-passing technology. We use Celery's RabbitMQ implementation, and we stumbled upon a great feature called Federation that allows us to partition our task queue across any number of RabbitMQ servers and gives us the confidence that, if any single server gets backlogged, others will pitch in and distribute some of the backlogged tasks to their consumers.

#MessageQueue

See more
Tim Abbott
Shared insights
on
RabbitMQRabbitMQPythonPythonRedisRedis
at

We've been using RabbitMQ as Zulip's queuing system since we needed a queuing system. What I like about it is that it scales really well and has good libraries for a wide range of platforms, including our own Python. So aside from getting it running, we've had to put basically 0 effort into making it scale for our needs.

However, there's several things that could be better about it: * It's error messages are absolutely terrible; if ever one of our users ends up getting an error with RabbitMQ (even for simple things like a misconfigured hostname), they always end up needing to get help from the Zulip team, because the errors logs are just inscrutable. As an open source project, we've handled this issue by really carefully scripting the installation to be a failure-proof configuration (in this case, setting the RabbitMQ hostname to 127.0.0.1, so that no user-controlled configuration can break it). But it was a real pain to get there and the process of determining we needed to do that caused a significant amount of pain to folks installing Zulip. * The pika library for Python takes a lot of time to startup a RabbitMQ connection; this means that Zulip server restarts are more disruptive than would be ideal. * It's annoying that you need to run the rabbitmqctl management commands as root.

But overall, I like that it has clean, clear semanstics and high scalability, and haven't been tempted to do the work to migrate to something like Redis (which has its own downsides).

See more
NServiceBus logo

NServiceBus

47
82
0
Enterprise-grade scalability and reliability for your workflows and integrations
47
82
+ 1
0
PROS OF NSERVICEBUS
    Be the first to leave a pro
    CONS OF NSERVICEBUS
      Be the first to leave a con

      related NServiceBus posts

      Azure Functions logo

      Azure Functions

      404
      433
      38
      Listen and react to events across your stack
      404
      433
      + 1
      38
      PROS OF AZURE FUNCTIONS
      • 11
        Pay only when invoked
      • 8
        Great developer experience for C#
      • 5
        Multiple languages supported
      • 5
        Great debugging support
      • 2
        Poor developer experience for C#
      • 2
        Easy scalability
      • 2
        Can be used as lightweight https service
      • 1
        Event driven
      • 1
        Azure component events for Storage, services etc
      • 1
        WebHooks
      CONS OF AZURE FUNCTIONS
        Be the first to leave a con

        related Azure Functions posts

        Kestas Barzdaitis
        Entrepreneur & Engineer · | 16 upvotes · 388.4K views

        CodeFactor being a #SAAS product, our goal was to run on a cloud-native infrastructure since day one. We wanted to stay product focused, rather than having to work on the infrastructure that supports the application. We needed a cloud-hosting provider that would be reliable, economical and most efficient for our product.

        CodeFactor.io aims to provide an automated and frictionless code review service for software developers. That requires agility, instant provisioning, autoscaling, security, availability and compliance management features. We looked at the top three #IAAS providers that take up the majority of market share: Amazon's Amazon EC2 , Microsoft's Microsoft Azure, and Google Compute Engine.

        AWS has been available since 2006 and has developed the most extensive services ant tools variety at a massive scale. Azure and GCP are about half the AWS age, but also satisfied our technical requirements.

        It is worth noting that even though all three providers support Docker containerization services, GCP has the most robust offering due to their investments in Kubernetes. Also, if you are a Microsoft shop, and develop in .NET - Visual Studio Azure shines at integration there and all your existing .NET code works seamlessly on Azure. All three providers have serverless computing offerings (AWS Lambda, Azure Functions, and Google Cloud Functions). Additionally, all three providers have machine learning tools, but GCP appears to be the most developer-friendly, intuitive and complete when it comes to #Machinelearning and #AI.

        The prices between providers are competitive across the board. For our requirements, AWS would have been the most expensive, GCP the least expensive and Azure was in the middle. Plus, if you #Autoscale frequently with large deltas, note that Azure and GCP have per minute billing, where AWS bills you per hour. We also applied for the #Startup programs with all three providers, and this is where Azure shined. While AWS and GCP for startups would have covered us for about one year of infrastructure costs, Azure Sponsorship would cover about two years of CodeFactor's hosting costs. Moreover, Azure Team was terrific - I felt that they wanted to work with us where for AWS and GCP we were just another startup.

        In summary, we were leaning towards GCP. GCP's advantages in containerization, automation toolset, #Devops mindset, and pricing were the driving factors there. Nevertheless, we could not say no to Azure's financial incentives and a strong sense of partnership and support throughout the process.

        Bottom line is, IAAS offerings with AWS, Azure, and GCP are evolving fast. At CodeFactor, we aim to be platform agnostic where it is practical and retain the flexibility to cherry-pick the best products across providers.

        See more
        Michal Nowak

        In a couple of recent projects we had an opportunity to try out the new Serverless approach to building web applications. It wasn't necessarily a question if we should use any particular vendor but rather "if" we can consider serverless a viable option for building apps. Obviously our goal was also to get a feel for this technology and gain some hands-on experience.

        We did consider AWS Lambda, Firebase from Google as well as Azure Functions. Eventually we went with AWS Lambdas.

        PROS
        • No servers to manage (obviously!)
        • Limited fixed costs – you pay only for used time
        • Automated scaling and balancing
        • Automatic failover (or, at this level of abstraction, no failover problem at all)
        • Security easier to provide and audit
        • Low overhead at the start (with the certain level of knowledge)
        • Short time to market
        • Easy handover - deployment coupled with code
        • Perfect choice for lean startups with fast-paced iterations
        • Augmentation for the classic cloud, server(full) approach
        CONS
        • Not much know-how and best practices available about structuring the code and projects on the market
        • Not suitable for complex business logic due to the risk of producing highly coupled code
        • Cost difficult to estimate (helpful tools: serverlesscalc.com)
        • Difficulty in migration to other platforms (Vendor lock⚠️)
        • Little engineers with experience in serverless on the job market
        • Steep learning curve for engineers without any cloud experience

        More details are on our blog: https://evojam.com/blog/2018/12/5/should-you-go-serverless-meet-the-benefits-and-flaws-of-new-wave-of-cloud-solutions I hope it helps 🙌 & I'm curious of your experiences.

        See more
        Kafka logo

        Kafka

        12.7K
        11.8K
        544
        Distributed, fault tolerant, high throughput pub-sub messaging system
        12.7K
        11.8K
        + 1
        544
        PROS OF KAFKA
        • 116
          High-throughput
        • 111
          Distributed
        • 84
          Scalable
        • 77
          High-Performance
        • 62
          Durable
        • 34
          Publish-Subscribe
        • 17
          Simple-to-use
        • 13
          Open source
        • 10
          Written in Scala and java. Runs on JVM
        • 6
          Message broker + Streaming system
        • 4
          Avro schema integration
        • 2
          Robust
        • 2
          KSQL
        • 2
          Suport Multiple clients
        • 2
          Partioned, replayable log
        • 1
          Fun
        • 1
          Extremely good parallelism constructs
        • 1
          Flexible
        • 1
          Simple publisher / multi-subscriber model
        CONS OF KAFKA
        • 25
          Non-Java clients are second-class citizens
        • 25
          Needs Zookeeper
        • 7
          Operational difficulties
        • 1
          Terrible Packaging

        related Kafka posts

        Eric Colson
        Chief Algorithms Officer at Stitch Fix · | 20 upvotes · 1.7M views

        The algorithms and data infrastructure at Stitch Fix is housed in #AWS. Data acquisition is split between events flowing through Kafka, and periodic snapshots of PostgreSQL DBs. We store data in an Amazon S3 based data warehouse. Apache Spark on Yarn is our tool of choice for data movement and #ETL. Because our storage layer (s3) is decoupled from our processing layer, we are able to scale our compute environment very elastically. We have several semi-permanent, autoscaling Yarn clusters running to serve our data processing needs. While the bulk of our compute infrastructure is dedicated to algorithmic processing, we also implemented Presto for adhoc queries and dashboards.

        Beyond data movement and ETL, most #ML centric jobs (e.g. model training and execution) run in a similarly elastic environment as containers running Python and R code on Amazon EC2 Container Service clusters. The execution of batch jobs on top of ECS is managed by Flotilla, a service we built in house and open sourced (see https://github.com/stitchfix/flotilla-os).

        At Stitch Fix, algorithmic integrations are pervasive across the business. We have dozens of data products actively integrated systems. That requires serving layer that is robust, agile, flexible, and allows for self-service. Models produced on Flotilla are packaged for deployment in production using Khan, another framework we've developed internally. Khan provides our data scientists the ability to quickly productionize those models they've developed with open source frameworks in Python 3 (e.g. PyTorch, sklearn), by automatically packaging them as Docker containers and deploying to Amazon ECS. This provides our data scientist a one-click method of getting from their algorithms to production. We then integrate those deployments into a service mesh, which allows us to A/B test various implementations in our product.

        For more info:

        #DataScience #DataStack #Data

        See more
        John Kodumal

        As we've evolved or added additional infrastructure to our stack, we've biased towards managed services. Most new backing stores are Amazon RDS instances now. We do use self-managed PostgreSQL with TimescaleDB for time-series data—this is made HA with the use of Patroni and Consul.

        We also use managed Amazon ElastiCache instances instead of spinning up Amazon EC2 instances to run Redis workloads, as well as shifting to Amazon Kinesis instead of Kafka.

        See more
        Sidekiq logo

        Sidekiq

        992
        508
        407
        Simple, efficient background processing for Ruby
        992
        508
        + 1
        407
        PROS OF SIDEKIQ
        • 123
          Simple
        • 99
          Efficient background processing
        • 60
          Scalability
        • 37
          Better then resque
        • 26
          Great documentation
        • 15
          Admin tool
        • 14
          Great community
        • 8
          Integrates with redis automatically, with zero config
        • 7
          Great support
        • 7
          Stupidly simple to integrate and run on Rails/Heroku
        • 3
          Ruby
        • 3
          Freeium
        • 2
          Pro version
        • 1
          Dashboard w/live polling
        • 1
          Great ecosystem of addons
        • 1
          Fast
        CONS OF SIDEKIQ
          Be the first to leave a con

          related Sidekiq posts

          Cyril Duchon-Doris

          We decided to use AWS Lambda for several serverless tasks such as

          • Managing AWS backups
          • Processing emails received on Amazon SES and stored to Amazon S3 and notified via Amazon SNS, so as to push a message on our Redis so our Sidekiq Rails workers can process inbound emails
          • Pushing some relevant Amazon CloudWatch metrics and alarms to Slack
          See more

          I'm building a new process management tool. I decided to build with Rails as my backend, using Sidekiq for background jobs. I chose to work with these tools because I've worked with them before and know that they're able to get the job done. They may not be the sexiest tools, but they work and are reliable, which is what I was optimizing for. For data stores, I opted for PostgreSQL and Redis. Because I'm planning on offering dashboards, I wanted a SQL database instead of something like MongoDB that might work early on, but be difficult to use as soon as I want to facilitate aggregate queries.

          On the front-end I'm using Vue.js and vuex in combination with #Turbolinks. In effect, I want to render most pages on the server side without key interactions being managed by Vue.js . This is the first project I'm working on where I've explicitly decided not to include jQuery . I have found React and Redux.js more confusing to setup. I appreciate the opinionated approach from the Vue.js community and that things just work together the way that I'd expect. To manage my javascript dependencies, I'm using Yarn .

          For CSS frameworks, I'm using #Bulma.io. I really appreciate it's minimal nature and that there are no hard javascript dependencies. And to add a little spice, I'm using #font-awesome.

          See more
          Resque logo

          Resque

          108
          95
          9
          A Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later
          108
          95
          + 1
          9
          PROS OF RESQUE
          • 5
            Free
          • 3
            Scalable
          • 1
            Easy to use on heroku
          CONS OF RESQUE
            Be the first to leave a con

            related Resque posts

            Beanstalkd logo

            Beanstalkd

            102
            122
            74
            A simple, fast work queue
            102
            122
            + 1
            74
            PROS OF BEANSTALKD
            • 23
              Fast
            • 12
              Free
            • 12
              Does one thing well
            • 9
              Scalability
            • 8
              Simplicity
            • 3
              Job delay
            • 3
              External admin UI developer friendly
            • 2
              Job prioritization
            • 2
              External admin UI
            CONS OF BEANSTALKD
              Be the first to leave a con

              related Beanstalkd posts

              Frédéric MARAND
              Core Developer at OSInet · | 2 upvotes · 168.5K views

              I used Kafka originally because it was mandated as part of the top-level IT requirements at a Fortune 500 client. What I found was that it was orders of magnitude more complex ...and powerful than my daily Beanstalkd , and far more flexible, resilient, and manageable than RabbitMQ.

              So for any case where utmost flexibility and resilience are part of the deal, I would use Kafka again. But due to the complexities involved, for any time where this level of scalability is not required, I would probably just use Beanstalkd for its simplicity.

              I tend to find RabbitMQ to be in an uncomfortable middle place between these two extremities.

              See more
              PHP-FPM logo

              PHP-FPM

              74
              79
              0
              An alternative FastCGI daemon for PHP
              74
              79
              + 1
              0
              PROS OF PHP-FPM
                Be the first to leave a pro
                CONS OF PHP-FPM
                  Be the first to leave a con

                  related PHP-FPM posts