Alternatives to Fireworq logo

Alternatives to Fireworq

Sidekiq, Resque, Beanstalkd, PHP-FPM, and Hangfire are the most popular alternatives and competitors to Fireworq.
0
4
+ 1
0

What is Fireworq and what are its top alternatives?

Fireworq is a lightweight, high-performance job queue system available from any programming language which can talk HTTP. It works with a single binary without external dependencies.
Fireworq is a tool in the Background Processing category of a tech stack.
Fireworq is an open source tool with 1.9K GitHub stars and 84 GitHub forks. Here鈥檚 a link to Fireworq's open source repository on GitHub

Fireworq alternatives & related posts

related Sidekiq posts

Simon Bettison
Simon Bettison
Managing Director at Bettison.org Limited | 7 upvotes 197.8K views
atBettison.org LimitedBettison.org Limited
PostgreSQL
PostgreSQL
Elasticsearch
Elasticsearch
Sidekiq
Sidekiq
Redis
Redis
Amazon ElastiCache
Amazon ElastiCache
Rails
Rails
RSpec
RSpec
Selenium
Selenium
Travis CI
Travis CI
Ruby
Ruby
Unicorn
Unicorn
nginx
nginx
Amazon CloudFront
Amazon CloudFront
Amazon SES
Amazon SES
Amazon SQS
Amazon SQS
Amazon Route 53
Amazon Route 53
Amazon VPC
Amazon VPC
Docker
Docker
Amazon EC2 Container Service
Amazon EC2 Container Service

In 2010 we made the very difficult decision to entirely re-engineer our existing monolithic LAMP application from the ground up in order to address some growing concerns about it's long term viability as a platform.

Full application re-write is almost always never the answer, because of the risks involved. However the situation warranted drastic action as it was clear that the existing product was going to face severe scaling issues. We felt it better address these sooner rather than later and also take the opportunity to improve the international architecture and also to refactor the database in. order that it better matched the changes in core functionality.

PostgreSQL was chosen for its reputation as being solid ACID compliant database backend, it was available as an offering AWS RDS service which reduced the management overhead of us having to configure it ourselves. In order to reduce read load on the primary database we implemented an Elasticsearch layer for fast and scalable search operations. Synchronisation of these indexes was to be achieved through the use of Sidekiq's Redis based background workers on Amazon ElastiCache. Again the AWS solution here looked to be an easy way to keep our involvement in managing this part of the platform at a minimum. Allowing us to focus on our core business.

Rails ls was chosen for its ability to quickly get core functionality up and running, its MVC architecture and also its focus on Test Driven Development using RSpec and Selenium with Travis CI providing continual integration. We also liked Ruby for its terse, clean and elegant syntax. Though YMMV on that one!

Unicorn was chosen for its continual deployment and reputation as a reliable application server, nginx for its reputation as a fast and stable reverse-proxy. We also took advantage of the Amazon CloudFront CDN here to further improve performance by caching static assets globally.

We tried to strike a balance between having control over management and configuration of our core application with the convenience of being able to leverage AWS hosted services for ancillary functions (Amazon SES , Amazon SQS Amazon Route 53 all hosted securely inside Amazon VPC of course!).

Whilst there is some compromise here with potential vendor lock in, the tasks being performed by these ancillary services are no particularly specialised which should mitigate this risk. Furthermore we have already containerised the stack in our development using Docker environment, and looking to how best to bring this into production - potentially using Amazon EC2 Container Service

See more
Cyril Duchon-Doris
Cyril Duchon-Doris
CTO at My Job Glasses | 5 upvotes 40.3K views
atMy Job GlassesMy Job Glasses
Redis
Redis
Rails
Rails
Sidekiq
Sidekiq
Amazon SQS
Amazon SQS

We migrated from Amazon SQS + Shoryuken to Sidekiq in order to have at-most-once delivery out of the box and more flexibility.

The UI builtin Rails makes it smoother for development and QA. Through the sidekiq rails engine we can easily see & understand which job is/was/will be executed, and even get some stats for free. Compared to SQS, we lose in scalability (need to manage the underlying Redis instance) but this is not so critical right now for our business size and the PROs clearly outweigh the CONs. Plugins allow to easily add distributed CRON scheduled jobs in there for almost free, and this is a core feature for us, so we no longer need to maintain a "scheduler" instance and we make our CRON jobs more resilient. The Sidekiq UI can easily be tweaked and for instance we have added a column that translates the CRON syntax into a human readable string, so it's easy for our Q/A to check whether the job is scheduled appropriately.

We still use Amazon SQS for some other apps, but no longer for our main Rails app.

See more
Resque logo

Resque

90
60
8
90
60
+ 1
8
A Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later
Resque logo
Resque
VS
Fireworq logo
Fireworq

related Beanstalkd posts

Fr茅d茅ric MARAND
Fr茅d茅ric MARAND
Core Developer at OSInet | 2 upvotes 122.5K views
atOSInetOSInet
Beanstalkd
Beanstalkd
RabbitMQ
RabbitMQ
Kafka
Kafka

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

43
33
0
43
33
+ 1
0
An alternative FastCGI daemon for PHP
    Be the first to leave a pro
    PHP-FPM logo
    PHP-FPM
    VS
    Fireworq logo
    Fireworq
    Hangfire logo

    Hangfire

    40
    27
    4
    40
    27
    + 1
    4
    Perform background processing in .NET and .NET Core applications
    Hangfire logo
    Hangfire
    VS
    Fireworq logo
    Fireworq
    delayed_job logo

    delayed_job

    39
    38
    6
    39
    38
    + 1
    6
    Database backed asynchronous priority queue -- Extracted from Shopify
    delayed_job logo
    delayed_job
    VS
    Fireworq logo
    Fireworq

    related delayed_job posts

    Jerome Dalbert
    Jerome Dalbert
    Senior Backend Engineer at StackShare | 4 upvotes 52.7K views
    atGratify CommerceGratify Commerce
    delayed_job
    delayed_job
    Rails
    Rails
    AWS Elastic Beanstalk
    AWS Elastic Beanstalk
    Sidekiq
    Sidekiq
    Ruby
    Ruby
    Amazon SQS
    Amazon SQS
    #BackgroundProcessing

    delayed_job is a great Rails background job library for new projects, as it only uses what you already have: a relational database. We happily used it during the company鈥檚 first two years.

    But it started to falter as our web and database transactions significantly grew. Our app interacted with users via SMS texts sent inside background jobs. Because the delayed_job daemon ran every couple seconds, this meant that users often waited several long seconds before getting text replies, which was not acceptable. Moreover, job processing was done inside AWS Elastic Beanstalk web instances, which were already under stress and not meant to handle jobs.

    We needed a fast background job system that could process jobs in near real-time and integrate well with AWS. Sidekiq is a fast and popular Ruby background job library, but it does not leverage the Elastic Beanstalk worker architecture, and you have to maintain a Redis instance.

    We ended up choosing active-elastic-job, which seamlessly integrates with worker instances and Amazon SQS. SQS is a fast queue and you don鈥檛 need to worry about infrastructure or scaling, as AWS handles it for you.

    We noticed significant performance gains immediately after making the switch.

    #BackgroundProcessing

    See more
    Jerome Dalbert
    Jerome Dalbert
    Senior Backend Engineer at StackShare | 3 upvotes 34K views
    atStackShareStackShare
    Sidekiq
    Sidekiq
    Ruby
    Ruby
    delayed_job
    delayed_job
    Redis
    Redis

    We use Sidekiq to process millions of Ruby background jobs a day under normal loads. We sometimes process more than that when running one-off backfill tasks.

    With so many jobs, it wouldn't really make sense to use delayed_job, as it would put our main database under unnecessary load, which would make it a bottleneck with most DB queries serving jobs and not end users. I suppose you could create a separate DB just for jobs, but that can be a hassle. Sidekiq uses a separate Redis instance so you don't have this problem. And it is very performant!

    I also like that its free version comes "batteries included" with:

    • A web monitoring UI that provides some nice stats.
    • An API that can come in handy for one-off tasks, like changing the queue of certain already enqueued jobs.

    Sidekiq is a pleasure to use. All our engineers love it!

    See more
    Kue logo

    Kue

    31
    42
    1
    31
    42
    + 1
    1
    Kue is a priority job queue backed by redis, built for node.js
    Kue logo
    Kue
    VS
    Fireworq logo
    Fireworq
    Bull logo

    Bull

    23
    27
    4
    23
    27
    + 1
    4
    Premium Queue package for handling jobs and messages in NodeJS
    Bull logo
    Bull
    VS
    Fireworq logo
    Fireworq