Displaying 1 to 20 from 35 results

recommendable - :+1::-1: A recommendation engine using Likes and Dislikes for your Ruby app

  •    Ruby

Recommendable is a gem that allows you to quickly add a recommendation engine for Likes and Dislikes to your Ruby application using my version of Jaccardian similarity and memory-based collaborative filtering. Bundling one of the queueing systems above is highly recommended to avoid having to manually refresh users' recommendations. If you bundle Sidekiq, you should also include 'sidekiq-middleware' in your Gemfile to ensure that a user will not get enqueued more than once at a time. If bundling Resque, you should include 'resque-loner' for this. As far as I know, there is no current way to avoid duplicate jobs in DelayedJob. Queueing for Torquebox is also supported.

sidekiq-cron - Scheduler / Cron for Sidekiq jobs

  •    Ruby

A scheduling add-on for Sidekiq. Runs a thread alongside Sidekiq workers to schedule jobs at specified times (using cron notation * * * * * parsed by Rufus-Scheduler, more about cron notation.

sidekiq-scheduler - Lightweight job scheduler extension for Sidekiq

  •    Ruby

sidekiq-scheduler is an extension to Sidekiq that pushes jobs in a scheduled way, mimicking cron utility. Note: If you are looking for version 2.2.*, go to 2.2-stable branch.

gush - Fast and distributed workflow runner using only Sidekiq and Redis

  •    Ruby

Gush is a parallel workflow runner using only Redis as storage and ActiveJob for scheduling and executing jobs. Gush relies on directed acyclic graphs to store dependencies, see Parallelizing Operations With Dependencies by Stephen Toub to learn more about this method.




sidekiq-unique-jobs - The missing unique jobs in sidekiq

  •    Ruby

See https://github.com/mperham/sidekiq#requirements for what is required. Starting from 5.0.0 only sidekiq >= 4 is supported and support for MRI <= 2.1 is dropped. Sidekiq consists of a client and a server. The client is responsible for pushing jobs to the queue and the worker is responsible for popping jobs from the queue. Most of the uniqueness is handled when the client is pushing jobs to the queue. The client checks if it is allowed to put a job on the queue. This is probably the most common way of locking.

sidekiq-statistic - See statistic about your workers

  •    Ruby

Improved display of statistics for your sidekiq workers and jobs. Open Statistic tab on your sidekiq page.

verk - A job processing system that just verks!

  •    Elixir

Verk is a job processing system backed by Redis. It uses the same job definition of Sidekiq/Resque. The goal is to be able to isolate the execution of a queue of jobs as much as possible.


worker-glass - Timeout and Reentrancy for your background processing workers

  •    Ruby

WorkerGlass provides optional timeout and after failure (reentrancy) for background processing worker engines (like Sidekiq, Resque, etc).If you don't know what is reentrancy, you can read about it here.

jobqueue - Jobqueue manages running and scheduling jobs (think Sidekiq or Resque for Go).

  •    Go

Jobqueue manages running and scheduling jobs (think Sidekiq or Resque). You can choose between MySQL and MongoDB as a backend for persistent storage.

chasqui - Chasqui adds persistent publish-subscribe (pub-sub) messaging capabilities to Sidekiq and Resque workers

  •    Ruby

Chasqui adds persistent publish-subscribe (pub-sub) messaging capabilities to Sidekiq and Resque workers. Chasqui uses Redis to store events and manage subscriptions. You can install Redis with your favorite package manager, such as homebrew, yum, or apt, or if you prefer, you can run vagrant up to run Redis in a virtual machine. If you already have Resque or Sidekiq working, then you already have everything you need to get started with Chasqui.

taskinator - A simple orchestration library for running complex processes or workflows in Ruby

  •    Ruby

A simple orchestration library for running complex processes or workflows in Ruby. Processes are defined using a simple DSL, where the sequences and tasks are defined. Processes can then be queued for execution. Sequences can be synchronous or asynchronous, and the overall process can be monitored for completion or failure. The configuration and state of each process and their respective tasks is stored using Redis key/values.

sidekiq-prometheus-exporter - All the basic metrics of Sidekiq prepared for Prometheus

  •    Ruby

Open dashboard example file, then open https://<your grafana-url>/dashboard/import and paste the content of the file.

Lumpik - Lumpik is the job queue system for general purpose.

  •    Swift

Lumpik is the job queue system for general purpose. Please host local redis-server at firtst. Do 100,000 no-op jobs, and measure its throughput.

docker-rails - Dockerized Rails app using ActionCable, Elasticsearch, Sidekiq and Yarn

  •    Ruby

Simple Rails 5.2 application to demonstrate using Docker for production deployment. The application is a very simple kind of CMS (content management system) allowing to manage posts. Beside the boring CRUD functionality it has some non-default features. This repo demonstrates my way of building Rails applications. The techniques used to build the app should not be considered as "best practice", maybe there are better ways to build. Any feedback would be appreciated.

sidecloq - Recurring / Periodic / Scheduled / Cron job extension for Sidekiq

  •    Ruby

There are several options for running periodic tasks with Sidekiq, including sidekiq-scheduler, sidekiq-cron, as well as Sidekiq Pro. Each tackles the problem slightly differently. Sidecloq is inspired by various facets of these projects, as well as resque-scheduler. I urge you to take a look at all of these options to see what works best for you. Tested on MRI > 2, JRuby and Rubinius. Basically, if you can run Sidekiq, you can run Sidecloq. Note that Sidekiq >= 5 does not support MRI ruby < 2.2.2.

sidekiq_profiling_middleware - Profile Sidekiq with StackProf & MemoryProfiler

  •    Ruby

Profile Sidekiq with StackProf & MemoryProfiler with optional support for S3 exports. The hooks provided by Ruby that are used by StackProf & MemoryProfiler are not able to distinguish threads well, so you will need to set your Sidekiq concurrency to 1. This will ensure that only one job operates at a time ensuring other jobs don't confuse your memory profile or stacktraces.

sidekiq-merger - Merge Sidekiq jobs

  •    Ruby

Merge sidekiq jobs occurring before the execution times. Inspired by sidekiq-grouping. Add merger option into your workers.

sidekiq_status - Extension to Sidekiq to pass job execution metadata such as status and result back to the client

  •    Ruby

If a job is rejected by some Client middleware, #perform_async returns false (as it does with ordinary Sidekiq worker). When a jobs is scheduled its status is waiting. As soon sidekiq worker begins job execution its status is changed to working. If the job successfully finishes (i.e. doesn't raise an unhandled exception) its status is complete. Otherwise its status is failed.





We have large collection of open source products. Follow the tags from Tag Cloud >>


Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.