A simple in-memory queue, for nodejs and the browser, with consumers for common usecases.
A simple in-memory queue, for nodejs and the browser, with consumers for common usecases.
Simple in-memory queue
Fast and simple in-memory queue implementation with configurable max concurrecy
A shim for the setImmediate efficient script yielding API
A simple tool to keep requests to be executed in order.
Promise queue with concurrency control
Tiny queue data structure
fast, tiny `queueMicrotask` shim for modern engines
A simple in-memory queue for easy sequential processing
Useful TypeScript utilities.
In memory queue system prioritizing tasks
Fast, in memory work queue
Local development World implementation for Workflow SDK
Simple JS queue with auto run for node and browsers
Miscellaneous indices for graphology.
A simple queue node that store incoming messages in memory queue and uses a feedback from a following action or trigger message to release the next message stored in the queue.
Task and Message Queues with Multiple Providers
High-priority task queue for Node.js and browsers
Simple JS queue with auto run for node and browsers
A simple in-memory queue that batches items together and releases them periodically. Useful for enforcing rate limits with APIs.
A really fast memory store for better-queue
A simple and lean driver-based service bus implementation
A simple key/value storage using files to persist the data
simple, on memory, and thread base job queue worker
Message provides flexible & reliable background/asynchronous job processing mechanism on top of simple queue interface. Any developer can create queue adapter for Message to hook up different messaging/queue system. One in-memory queue is included with Message for you to start development and test, and you can easily swap in other queues later.
Compatible with Resque 1.x. Use Resque.push if you are using >= 2.x. Resque is great. So is job processing with redis. Our biggest drawback has been that resque requires the class that will be processing a job to be loaded when the job is enqueued. But what happens when the implementing job is defined in a separate application and isn't currently loaded into memory? Enter Resque Remote. Resque Remote's simple goal is to allow you to add a job to a queue with a string identifier for the class rather than the class constant. It is assumed that the worker-side of the equation _will_ have the class in memory and hence will be able to run it no problem. Feedback, comments and questions are welcome at bj [dot] neilsen [at] gmail [dot] com.