A durable message queue library powered by the Redis' reliable queue pattern and LUA scripts
Redis-backed durable message queue
Durable message queue backed by SQLite. Inspired by goqite.
Build real-time applications powered by [Durable Objects](https://developers.cloudflare.com/durable-objects/), inspired by [PartyKit](https://www.partykit.io/).
Task and Message Queues with Multiple Providers
Tiny queue data structure
Safe access to VatData global
fast, tiny `queueMicrotask` shim for modern engines
Simple JS queue with auto run for node and browsers
A Node.js library for interacting with the Vercel Queue Service API
A Typescript framework built on the database
Simple JS queue with auto run for node and browsers
A shim for the setImmediate efficient script yielding API
A really simple message queue based on Redis
TypeScript SDK for Absurd - PostgreSQL-based durable task execution
Promise queue with concurrency control
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.
A simple tool to keep requests to be executed in order.
queue-lit is a tiny queue data structure in case you `Array#push()` or `Array#shift()` on large arrays very often
The smallest and simplest JavaScript priority queue
SQS adapter for message-queue-toolkit
- Flexible: Leverage the strenghts of Cloudflare abstractions and let app developers choose right setup for their use case (configurable transports/storage) - Efficient: Let's Durable Objects hibernate when not possible to avoid CPU billing while still st
amqplib wrapper for Rabbit MQ
Next tick shim that prefers process.nextTick over queueMicrotask for compat
Remq is a Redis-based protocol for building fast, durable message queues. The Remq protocol is defined by a collection of Lua scripts (located at https://github.com/kainosnoema/remq) which effectively turn Redis into a capable message queue broker for fast inter-service communication. The Remq Ruby client library is built on top of these scripts, making it easy to build fast, durable message queues.
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.