Redis Queue

Skill Profile

(Select at least one profile to enable specific modules)

• DevOps
• Backend
• Frontend
• AI-RAG
• Security Critical

Overview

Comprehensive guide to Redis as a message queue using Bull and BullMQ for Node.js applications. This skill covers queue setup, job creation and processing, job priorities, delayed jobs, repeatable jobs (cron), job lifecycle management, error handling, retries with backoff, queue monitoring, scaling workers, and production patterns including graceful shutdown and health checks.

Why This Matters

Redis with Bull/BullMQ provides a powerful, fast, and feature-rich queue system for Node.js applications. Understanding Redis queue patterns is essential for building scalable, reliable, and efficient job processing systems.

Core Concepts & Rules

1. Core Principles

• Follow established patterns and conventions
• Maintain consistency across codebase
• Document decisions and trade-offs

2. Implementation Guidelines

• Start with the simplest viable solution
• Iterate based on feedback and requirements
• Test thoroughly before deployment

Inputs / Outputs / Contracts

Skill Composition

• Depends on: None
• Compatible with: None
• Conflicts with: None
• Related Skills: None

Quick Start / Implementation Example

1. Review requirements and constraints
2. Set up development environment
3. Implement core functionality following patterns
4. Write tests for critical paths
5. Run tests and fix issues
6. Document any deviations or decisions

# Example implementation following best practices
def example_function():
    # Your implementation here
    pass

Assumptions

• Redis server is properly configured and accessible
• Network connectivity between workers and Redis
• Sufficient Redis memory for job storage
• Appropriate permissions for Redis operations
• Proper resource allocation for workers

Compatibility

• BullMQ: 3.0+ (recommended)
• Bull: 4.0+ (legacy)
• Redis: 6.0+
• Node.js: 14+
• TypeScript: 4.0+
• ioredis: 5.0+

Test Scenario Matrix (QA Strategy)

Technical Guardrails & Security Threat Model

1. Security & Privacy (Threat Model)

• Top Threats: Injection attacks, authentication bypass, data exposure

• Data Handling: Sanitize all user inputs to prevent Injection attacks. Never log raw PII
• Secrets Management: No hardcoded API keys. Use Env Vars/Secrets Manager
• Authorization: Validate user permissions before state changes

2. Performance & Resources

• Execution Efficiency: Consider time complexity for algorithms
• Memory Management: Use streams/pagination for large data
• Resource Cleanup: Close DB connections/file handlers in finally blocks

3. Architecture & Scalability

• Design Pattern: Follow SOLID principles, use Dependency Injection
• Modularity: Decouple logic from UI/Frameworks

4. Observability & Reliability

• Logging Standards: Structured JSON, include trace IDs request_id
• Metrics: Track error_rate, latency, queue_depth
• Error Handling: Standardized error codes, no bare except
• Observability Artifacts:
  • Log Fields: timestamp, level, message, request_id
  • Metrics: request_count, error_count, response_time
  • Dashboards/Alerts: High Error Rate > 5%

Agent Directives & Error Recovery

(ข้อกำหนดสำหรับ AI Agent ในการคิดและแก้ปัญหาเมื่อเกิดข้อผิดพลาด)

• Thinking Process: Analyze root cause before fixing. Do not brute-force.
• Fallback Strategy: Stop after 3 failed test attempts. Output root cause and ask for human intervention/clarification.
• Self-Review: Check against Guardrails & Anti-patterns before finalizing.
• Output Constraints: Output ONLY the modified code block. Do not explain unless asked.

Definition of Done (DoD) Checklist

• Tests passed + coverage met
• Lint/Typecheck passed
• Logging/Metrics/Trace implemented
• Security checks passed
• Documentation/Changelog updated
• Accessibility/Performance requirements met (if frontend)

Anti-patterns

1. Not using retries: Always configure retry attempts and backoff
2. Ignoring job priorities: Use priorities for critical tasks
3. No graceful shutdown: Implement proper shutdown handling
4. Not monitoring: Monitor queue depths and worker health
5. Large job payloads: Keep job data small (< 1MB)
6. No idempotency: Design jobs to be idempotent
7. Ignoring failures: Monitor and handle failed jobs
8. No cleanup: Configure removeOnComplete/removeOnFail

Reference Links & Examples

• Internal documentation and examples
• Official documentation and best practices
• Community resources and discussions

Versioning & Changelog

• Version: 1.0.0
• Changelog:
  • 2026-02-22: Initial version with complete template structure