System for managing queues, supporting priority and delayed job processing.
Voice Announcement Library for Queue Management System
redis queue management system
Tiny queue data structure
A seamless job queue management system for efficient task processing and workload distribution.
fast, tiny `queueMicrotask` shim for modern engines
In memory queue system prioritizing tasks
A shim for the setImmediate efficient script yielding API
Promise queue with concurrency control
A simple tool to keep requests to be executed in order.
Call an array of promise-returning functions, restricting concurrency to a specified limit.
The smallest and simplest JavaScript priority queue
queue-lit is a tiny queue data structure in case you `Array#push()` or `Array#shift()` on large arrays very often
Next tick shim that prefers process.nextTick over queueMicrotask for compat
Database-specific job handling and queue management
OCI NodeJS client for Queue Service
Promise-based queue
Simple JS queue with auto run for node and browsers
LRU Queue
@sidequest/core is the core package of SideQuest, a distributed background job queue for Node.js and TypeScript applications.
The fastest javascript implementation of a double-ended queue. Used by the official Redis, MongoDB, MariaDB & MySQL libraries for Node.js and many other libraries. Maintains compatability with deque.
Emulate AWS λ and SQS locally when developing your Serverless project
Simple JS queue with auto run for node and browsers
larksuite open sdk for nodejs
Monitor and manage jobs in a live Sneakers/ActiveJob queue system
A modern, real-time web interface for monitoring and managing Sidekiq queues. Features include live queue statistics, pause/resume operations, process limit management, bulk operations, and a responsive UI with zero configuration required. Perfect for production environments requiring professional queue monitoring capabilities. Built with Rails 7+ and shadcn-inspired design system for optimal user experience.
An AMQP-based background worker system for Ruby designed to make managing heterogenous tasks relatively easy. The use case for Woodhouse is for reliable and sane performance in situations where jobs on a single queue may vary significantly in length. The goal is to permit large numbers of quick jobs to be serviced even when many slow jobs are in the queue. A secondary goal is to provide a sane way for jobs on a given queue to be given special priority or dispatched to a server more suited to them. Clients (i.e., your application) may be using either Ruby 1.9 in any VM.
Triage system for cognitive overload. Classifies incoming demands by severity and urgency, routes to appropriate processing queues, and manages cognitive capacity under pressure.
Telework is a Resque plugin aimed at controlling Resque workers from the web UI. It makes it easy to manage workers on a complex systems that may include several hosts, different queue(s) and an evolving source code that is deployed several times a day. Beyond starting and stopping workers on remote hosts, the plugin makes it easy to switch between code revisions, gives a partial view of each worker's log (stdout and stderr) and maintains a status of each workers.
pikuri-memory gives a pikuri-core agent durable, long-lived memory: facts about the user and their work that persist across conversations. It wires a +recall+ tool plus an automatic per-turn prefetch onto an agent via +c.add_extension Pikuri::Memory::Extension.new(...)+ inside the +Agent.new+ block — same opt-in shape as +pikuri-tasks+ / +pikuri-vectordb+. Recall is automatic and synchronous (embed + vector search, milliseconds); capture is automatic and asynchronous (an off-the-interaction-path extraction queue), so a turn never blocks on "what should I remember?". Storage is mem0 (https://github.com/mem0ai/mem0) reached over a thin Faraday HTTP client — the append-only +add+ / read-time +search+ model. Only the *user's own words* are fed to extraction (a write-side hygiene rule that structurally drops system/assistant/tool-sourced junk), and recalled context enters the chat as a +:system+ message so it is provenance-tagged and excluded from the next extraction pass. This release ships the Ruby client + extension + tool against a *bring-your-own* mem0 endpoint; a self-managed mem0 sidecar supervisor (the +ChromaServer+-style docker pattern) is a follow-on.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.