repository·next·Indexed 20 days ago
https://github.com/weyoss/redis-smqA high-performance Redis-backed message queue for Node.js supporting FIFO, LIFO, and Priority queue types. Features include flexible routing, scheduling, rate limiting, and worker threads. The ecosystem includes the redis-smq-common library for foundational primitives like backoff strategies and worker management, a benchmarking suite for measuring producer and consumer throughput, and CI tools for changelog consolidation and GitHub release synchronization.
RedisSMQ is a high-performance, Redis-backed message queue library for Node.js. It provides a process-wide API for managing message flows using various queue types and routing models.
Key Capabilities:
The RedisSMQ REST API provides an HTTP interface that allows any web-capable application to interact with RedisSMQ message queues using a RESTful API.
Key features include:
RedisSMQ is a Redis-backed Message Queue (MQ) designed for robustness and simplicity. It provides various queue and delivery models, along with producer/consumer APIs. It is designed to be production-ready and easy to operate, with optional integration for a REST API and Web UI to assist with monitoring and administration.
Key features include:
ioredis or the official @redis/client.The RedisSMQ Web UI provides a graphical interface for managing your message queues. Key capabilities include:
ack (acknowledge), retry, and delete directly from the UI.The RedisSMQ Web UI provides the following capabilities:
ack, retry, delete).RedisSMQ is a high-performance, Redis-backed message queue for Node.js. It provides a simplified, process-wide API designed for low latency and operational simplicity.
An ExchangeFanout is a fanout exchange used for broadcasting messages to all bound queues. It routes messages to every queue bound to the exchange while ignoring any routing keys. This is the ideal mechanism for implementing pub/sub (publisher/subscriber) patterns where every consumer is intended to receive the same message.
const fanoutExchange = new ExchangeFanout();
// Bind a queue
await fanoutExchange.bindQueue('notifications', 'broadcast');
// Match all bound queues
const queues = await fanoutExchange.matchQueues('broadcast');RedisSMQ provides three exchange types for different routing requirements:
Routes messages to queues that have an exact match for the provided routing key.
Routes messages using pattern matching on dot-separated words:
* matches exactly one word.# matches zero or more words.user.# matches user.login, user.login.success, etc.Broadcasts every message to every queue bound to the exchange. No routing key is required or used.
// Direct
const msg = new ProducibleMessage()
.setDirectExchange('payments')
.setExchangeRoutingKey('payment.processed')
.setBody({ amount: 99.99 });
// Topic
const msg = new ProducibleMessage()
.setTopicExchange('events')
.setExchangeRoutingKey('user.login.success')
.setBody({ userId: 123 });
// Fanout
const msg = new ProducibleMessage()
.setFanoutExchange('alerts')
.setBody({ alert: 'System down!' });The QueueOperationValidator class is used to determine if specific operations are permitted on a queue based on its current state. Understanding these states is critical to preventing runtime errors when attempting to produce, consume, or manage queues.
| Queue State | Allowed Operations |
|---|---|
| ACTIVE | All operations are permitted. |
| PAUSED | All operations are permitted except CONSUME. |
| STOPPED | Only management operations are permitted (e.g., purge, delete, rate limits, consumer groups, exchanges). |
| LOCKED | No operations are allowed. |
A ProducibleMessage must have exactly one target destination. You can route messages directly to a queue or through various exchange types:
| Target Type | Method | Routing Key Required? |
| :--- | :--- | : |
| Queue | .setQueue('name') | No |
| Direct Exchange | .setDirectExchange('name') | Yes (via .setExchangeRoutingKey()) |
| Topic Exchange | .setTopicExchange('name') | Yes (via .setExchangeRoutingKey()) |
| Fanout Exchange | .setFanoutExchange('name') | No (Routing key is ignored) |
// Direct Exchange example
const msg = new ProducibleMessage()
.setDirectExchange('orders')
.setExchangeRoutingKey('order.created')
.setBody({ orderId: '123' });
// Topic Exchange example
const msg = new ProducibleMessage()
.setTopicExchange('events')
.setExchangeRoutingKey('user.created')
.setBody({ userId: 456 });
// Fanout Exchange example
const msg = new ProducibleMessage()
.setFanoutExchange('notifications')
.setBody({ alert: 'System update' });