Sucker Punch
Resque
Our great sponsors
Sucker Punch | Resque | |
---|---|---|
2 | 5 | |
2,654 | 9,385 | |
- | 0.1% | |
4.3 | 4.1 | |
4 months ago | 5 months ago | |
Ruby | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Sucker Punch
-
Simple Thread/Server question
I would suggest you use something like sucker punch to do this https://github.com/brandonhilkert/sucker_punch
-
Asynchronous Background Processing for Ruby or Rails using AWS Lambda Extensions.
Ever since writing this post last year on Using New Relic APM with Rails on AWS Lambda, I have always wanted to find a way to send APM data in a way that did not add extra milliseconds to the application's response times. Likewise, for smaller projects it would be nice to have a lightweight alternative to Lambdakiq for ActiveJob similar to Brandon Hilkert's popular SuckerPunch gem. Today we have both with the LambdaPunch gem.
Resque
-
Mike Perham of Sidekiq: “If you build something valuable, charge money for it.”
The free version acts exactly like Resque, the previous market leader in Ruby background jobs. If it was good enough reliability for GitHub and Shopify to use for years, it was good enough for Sidekiq OSS too.
Here's Resque literally using `lpop` which is destructive and will lose jobs.
https://github.com/resque/resque/blob/7623b8dfbdd0a07eb04b19...
-
Add web scraping data into the database at regular intervals [ruby & ror]
You can use a background job queue like Resque to scrape and process data in the background, and a scheduler like resque-scheduler to schedule jobs to run your scraper periodically.
-
How to run a really long task from a Rails web request
So how do we trigger such a long-running process from a Rails request? The first option that comes to mind is a background job run by some of the queuing back-ends such as Sidekiq, Resque or DelayedJob, possibly governed by ActiveJob. While this would surely work, the problem with all these solutions is that they usually have a limited number of workers available on the server and we didn’t want to potentially block other important background tasks for so long.
-
Building a dynamic staging platform
Background jobs are another limitation. Since only the Aha! web service runs in a dynamic staging, the host environment's workers would process any Resque jobs that were sent to the shared Redis instance. If your branch hadn't updated any background-able methods, this would be no big deal. But if you were hoping to test changes to these methods, you would be out of luck.
-
Autoscaling Redis applications on Kubernetes 🚀🚀
Redis Lists are quite versatile and used as the backbone for implementing scalable architectural patterns such as consumer-producer (based on queues), where producer applications push items into a List, and consumers (also called workers) process those items. Popular projects such as resque, sidekiq, celery etc. use Redis behind the scenes to implement background jobs.
What are some alternatives?
Sidekiq - Simple, efficient background processing for Ruby
Delayed::Job - Database based asynchronous priority queue system -- Extracted from Shopify
Shoryuken - A super efficient Amazon SQS thread based message processor for Ruby
Gush - Fast and distributed workflow runner using ActiveJob and Redis
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
Sneakers - A fast background processing framework for Ruby and RabbitMQ
Backburner - Simple and reliable beanstalkd job queue for ruby
good_job - Multithreaded, Postgres-based, Active Job backend for Ruby on Rails.
Karafka - Ruby and Rails efficient multithreaded Kafka processing framework
Que - A Ruby job queue that uses PostgreSQL's advisory locks for speed and reliability.