@anyq/memory

In-memory queue adapter for anyq - perfect for testing and development.

Installation

npm install @anyq/memory @anyq/core

Usage

import { MemoryProducer, MemoryConsumer } from '@anyq/memory';

// Create producer
const producer = new MemoryProducer({
  queue: 'my-queue'
});

// Create consumer
const consumer = new MemoryConsumer({
  queue: 'my-queue'
});

await producer.connect();
await consumer.connect();

// Subscribe to messages
await consumer.subscribe(async (message) => {
  console.log('Received:', message.data);
  await message.ack();
});

// Publish messages
await producer.publish({ hello: 'world' });
await producer.publishBatch([
  { order: 1 },
  { order: 2 }
]);

// Cleanup
await consumer.disconnect();
await producer.disconnect();

Configuration

interface MemoryQueueConfig {
  queue: string;           // Queue name
  maxSize?: number;        // Max messages in queue (default: unlimited)
  deliveryDelay?: number;  // Delay before message delivery (ms)
}

Features

• No external dependencies
• Perfect for unit tests
• Supports ack/nack
• Message persistence during session
• Batch publishing

Retry strategies (0.3.0)

This adapter participates in the opt-in pluggable retry strategies from @anyq/core. Pass a strategy via BaseQueueConfig.strategy and MemoryConsumer.applyStrategy() takes over per-message error handling; omit it and the legacy DLQ-after-maxDeliveryAttempts path runs unchanged.

| Capability | Support | |---|---| | supportsNativeDelay | true | | Native park | setTimeout re-enqueue onto the same queue | | Native deadLetterMessage | routes via the existing MemoryQueue.deadLetter() so x-death-reason / x-original-queue headers are preserved |

import { retryThenDeadLetter } from '@anyq/core';

const consumer = new MemoryConsumer({
  driver: 'memory',
  queueName: 'orders',
  strategy: retryThenDeadLetter({ maxAttempts: 5 }),
});

See @anyq/core for the full strategy catalogue and the apps/examples/retry-strategies workspace for runnable demos.

License

MIT