BullMQ 实战指南用 bullmq-specialist 技能构建生产级 Redis 任务队列与后台异步处理【免费下载链接】agentic-awesome-skillsAAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,600 agentic skills. Includes CLI, local MCP, catalog, plugins, and Workbench.项目地址: https://gitcode.com/GitHub_Trending/an/agentic-awesome-skills导读本指南以本仓库中bullmq-specialist技能SKILL.md为核心骨架系统讲解如何在 Node.js/TypeScript 应用中基于 Redis 构建可靠的任务队列、延迟任务、定时任务与多步骤 Job Flow。读完本文你将掌握 BullMQ 的队列/Worker/事件三大核心对象的使用方式、生产级配置要点重试、退避、限流、并发控制、优雅关闭以及可复用的技能协作栈邮件、后台处理、AI 流水线、定时任务并能对照技能内置的 11 项 Validation Checks 自查代码质量。说明该技能在仓库中的登记路径为 skills/bullmq-specialist/SKILL.md元数据catalog.json中描述其为 BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications归属framework类别来源为vibeship-spawner-skills (Apache 2.0)风险等级为none。一、设计原则生产队列的正确心智模型技能开篇给出 8 条核心原则是理解 BullMQ 一切用法的基础Producer 侧 fire-and-forget任务入队后即返回投递与可靠性交给队列本身总是显式设置 Job OptionsBullMQ 的默认值很少符合真实业务场景幂等是调用方自己的责任任务可能被执行不止一次业务处理必须可重入退避策略防止惊群效应指数退避exponential优于线性退避linear死信队列不是可选项失败任务必须有归属通过removeOnFail保留或单独队列承接并发上限保护下游起步应保守再逐步上调任务数据保持精简传 ID 而不是完整对象降低 Redis 内存压力优雅关闭防止孤儿任务正确处理 SIGTERM。这些原则直接映射到技能 Capabilities 清单bullmq-queues、job-scheduling、delayed-jobs、repeatable-jobs、job-priorities、rate-limiting-jobs、job-events、worker-patterns、flow-producers、job-dependencies。二、工具链选型技能的 Tooling 部分给出了从核心依赖到运维监控的完整选型核心bullmq队列主库、ioredisRedis 客户端托管upstash、redis-cloud、elasticache、railway按需选择托管 Redis监控bull-board、arena、bullmq-pro可视化队列看板模式delayed-jobs、repeatable-jobs、job-flows、rate-limiting、sandboxed-processors沙箱化处理器。Scope 部分同时划清了职责边界redis-infrastructure交给redis-specialist、serverless-queues交给upstash-qstash、复杂workflow-orchestration交给temporal-craftsman、event-sourcing交给event-architect、email-delivery交给email-systems——即本技能只负责队列本身的工程实现不做跨界包揽。三、核心模式实战从入门到 Job Flow3.1 基础队列搭建生产就绪配置技能给出的基础示例涵盖了 Queue、Worker、QueueEvents 与共享 Redis 连接import { Queue, Worker, QueueEvents } from bullmq; import IORedis from ioredis; // 所有队列共享同一个连接 const connection new IORedis(process.env.REDIS_URL, { maxRetriesPerRequest: null, // BullMQ 必需项 enableReadyCheck: false, }); // 带合理默认值的队列 const emailQueue new Queue(emails, { connection, defaultJobOptions: { attempts: 3, backoff: { type: exponential, delay: 1000, }, removeOnComplete: { count: 1000 }, removeOnFail: { count: 5000 }, }, }); // 带并发上限的 Worker const worker new Worker(emails, async (job) { await sendEmail(job.data); }, { connection, concurrency: 5, limiter: { max: 100, duration: 60000, // 每分钟 100 个任务 }, }); // 事件监听 worker.on(failed, (job, err) { console.error(Job ${job?.id} failed:, err); });要点解析maxRetriesPerRequest: null是 BullMQ 的硬性要求否则 Redis 连接异常会导致 Worker 停止工作对应 Validation Checks 中的 ERROR 级检查defaultJobOptions将重试次数、指数退避、完成/失败保留策略固化到队列级避免每个任务重复配置removeOnComplete: { count: 1000 }/removeOnFail: { count: 5000 }用保留最近 N 条代替无限堆积控制 Redis 内存占用limiter实现队列级速率限制concurrency控制并发两者配合既保护 Redis 又保护下游服务数据库连接池、第三方 API 限流。3.2 延迟任务与定时Repeatable任务技能用三个调用覆盖调度场景// 延迟任务24 小时后执行一次 await queue.add(reminder, { userId: 123 }, { delay: 24 * 60 * 60 * 1000, // 24 hours }); // 定时任务每天 9 点执行显式时区 await queue.add(daily-digest, { type: summary }, { repeat: { pattern: 0 9 * * *, // 每天 9am tz: America/New_York, }, }); // 移除定时任务 await queue.removeRepeatable(daily-digest, { pattern: 0 9 * * *, tz: America/New_York, });两个关键坑位在技能 Validation Checks 中单独列出Repeatable job without explicit timezoneWARNING——不指定时区会用服务器本地时间跨夏令时DST会出现漂移因此tz参数应视为必填Retry without backoff strategyWARNING——有重试但没有退避会造成惊群效应。3.3 Job Flows多步骤任务编排与依赖FlowProducer 让父任务等待所有子任务完成成为一等公民import { FlowProducer } from bullmq; const flowProducer new FlowProducer({ connection }); // 父任务等待所有子任务完成后继续 await flowProducer.add({ name: process-order, queueName: orders, data: { orderId: 123 }, children: [ { name: validate-inventory, queueName: inventory, data: { orderId: 123 }, }, { name: charge-payment, queueName: payments, data: { orderId: 123 }, }, { name: notify-warehouse, queueName: notifications, data: { orderId: 123 }, }, ], });这是技能 Capabilities 中flow-producers与job-dependencies的具体落地库存校验、扣款、仓库通知三个子任务可以并行执行且分属不同队列父任务process-order会在全部子任务成功后才被触发天然实现多阶段、有依赖、可并行的复杂流程。结合原则 7子任务数据同样只传orderId这类 ID 而非完整对象。3.4 优雅关闭部署时零任务丢失Worker 直接被杀掉会留下孤儿任务技能的关闭流程是const shutdown async () { console.log(Shutting down gracefully...); // 1. 停止接收新任务 await worker.pause(); // 2. 等待当前任务执行完成可加超时 await worker.close(); // 3. 关闭队列连接 await queue.close(); process.exit(0); }; process.on(SIGTERM, shutdown); process.on(SIGINT, shutdown);顺序上有讲究先pause()停止消费再close()等待在途任务收尾最后关闭连接。技能在 Validation Checks 中将No graceful shutdown handling标记为 WARNING——缺失时部署/重启会造成任务孤儿化。3.5 Bull Board 可视化看板需要可见性时技能推荐 bull-board 系列import { createBullBoard } from bull-board/api; import { BullMQAdapter } from bull-board/api/bullMQAdapter; import { ExpressAdapter } from bull-board/express; const serverAdapter new ExpressAdapter(); serverAdapter.setBasePath(/admin/queues); createBullBoard({ queues: [ new BullMQAdapter(emailQueue), new BullMQAdapter(orderQueue), ], serverAdapter, }); app.use(/admin/queues, serverAdapter.getRouter());挂载后即可在/admin/queues可视化查看队列状态、任务状态分布与失败详情与技能 Tooling 中的bull-board、arena对应。四、Validation Checks把经验固化为可执行检查技能最有工程价值的产出是 11 项代码检查含严重级别与告警文案可直接沉淀为 Lint 规则或 Code Review 清单检查项级别核心信息Redis 连接缺少maxRetriesPerRequestERROR缺省会导致 Redis 异常时 Worker 停摆无 stalled 事件处理器WARNINGstalled 任务提示 Worker 崩溃应监控无 failed 事件处理器WARNING失败任务应记录日志并告警无优雅关闭处理WARNING部署时任务可能被孤儿化请求处理器中 await queue.addINFO建议 fire-and-forget 以加快响应任务数据可能过大WARNING传 ID 而非完整对象控制 Redis 内存任务无超时配置INFO建议设置 timeout 防卡死有重试但无退避策略WARNING应使用指数退避防惊群定时任务未指定时区WARNING服务器本地时间会随 DST 漂移Worker 并发可能过高INFO确认下游DB 连接、API 限流能承受请求处理器阻塞入队INFO入队应异步、快速返回这些检查与第三节的代码模式一一对应可作为代码写完自检一遍的 checklist。五、协作栈与其他技能组合的实战编排技能的 Collaboration 部分定义了委托触发词与多技能工作流体现了本仓库技能组合的工程理念委托触发触发词 → 目标技能redis infrastructure|redis cluster|memory tuning→redis-specialist队列依赖 Redis 基础设施serverless queue|edge queue|no redis→upstash-qstash不想自管 Rediscomplex workflow|saga|compensation|long-running→temporal-craftsman超出简单 Job 的编排event sourcing|CQRS|event streaming→event-architectdeploy|kubernetes|scaling|infrastructure→devopsmonitor|metrics|alerting|dashboard→performance-hunter。Email Queue Stackbullmq-specialistemail-systemsredis-specialist1. Email request received (API) 2. Job queued with rate limiting (bullmq-specialist) 3. Worker processes with backoff (bullmq-specialist) 4. Email sent via provider (email-systems) 5. Status tracked in Redis (redis-specialist)Background Processing Stackbullmq-specialistbackenddevops1. API receives request (backend) 2. Long task queued for background (bullmq-specialist) 3. Worker processes async (bullmq-specialist) 4. Result stored/notified (backend) 5. Workers scaled per load (devops)AI Processing Pipelinebullmq-specialistai-workflow-automationperformance-hunter1. AI task submitted (ai-workflow-automation) 2. Job flow created with dependencies (bullmq-specialist) 3. Workers process stages (bullmq-specialist) 4. Performance monitored (performance-hunter) 5. Results aggregated (ai-workflow-automation)Scheduled Tasks Stackbullmq-specialistbackendredis-specialist1. Repeatable jobs defined (bullmq-specialist) 2. Cron patterns with timezone (bullmq-specialist) 3. Jobs execute on schedule (bullmq-specialist) 4. State managed in Redis (redis-specialist) 5. Results handled (backend)技能还声明了推荐搭配redis-specialist、backend、nextjs-app-router、email-systems、ai-workflow-automation、performance-hunter。六、触发条件与使用边界When to Use当用户提到bullmq、bull queue、redis queue、background job、job queue、delayed job、repeatable job、worker process、job scheduling、async processing等关键词时触发。Limitations务必遵守仅当任务与上述 Scope 明确匹配时使用本技能技能输出不能替代环境特定的验证、测试或专家评审当缺少必要输入、权限、安全边界或成功标准时停下来向用户澄清。总结bullmq-specialist技能把 BullMQ 生产实践浓缩为一套原则—模式—检查—协作四层体系8 条设计原则指导心智模型5 组代码模式覆盖入队、调度、依赖编排、优雅关闭与可视化11 项 Validation Checks 把经验固化为可执行的自查清单4 个协作栈展示了如何与redis-specialist、email-systems、devops等技能组合解决真实业务问题。对于要在 Node.js/TypeScript 中落地 Redis 任务队列的开发者本文档可作为从 0 到生产可用的完整参考。【免费下载链接】agentic-awesome-skillsAAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,600 agentic skills. Includes CLI, local MCP, catalog, plugins, and Workbench.项目地址: https://gitcode.com/GitHub_Trending/an/agentic-awesome-skills创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考
BullMQ 实战指南用 bullmq-specialist 技能构建生产级 Redis 任务队列与后台异步处理【免费下载链接】agentic-awesome-skillsAAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,600 agentic skills. Includes CLI, local MCP, catalog, plugins, and Workbench.项目地址: https://gitcode.com/GitHub_Trending/an/agentic-awesome-skills导读本指南以本仓库中bullmq-specialist技能SKILL.md为核心骨架系统讲解如何在 Node.js/TypeScript 应用中基于 Redis 构建可靠的任务队列、延迟任务、定时任务与多步骤 Job Flow。读完本文你将掌握 BullMQ 的队列/Worker/事件三大核心对象的使用方式、生产级配置要点重试、退避、限流、并发控制、优雅关闭以及可复用的技能协作栈邮件、后台处理、AI 流水线、定时任务并能对照技能内置的 11 项 Validation Checks 自查代码质量。说明该技能在仓库中的登记路径为 skills/bullmq-specialist/SKILL.md元数据catalog.json中描述其为 BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications归属framework类别来源为vibeship-spawner-skills (Apache 2.0)风险等级为none。一、设计原则生产队列的正确心智模型技能开篇给出 8 条核心原则是理解 BullMQ 一切用法的基础Producer 侧 fire-and-forget任务入队后即返回投递与可靠性交给队列本身总是显式设置 Job OptionsBullMQ 的默认值很少符合真实业务场景幂等是调用方自己的责任任务可能被执行不止一次业务处理必须可重入退避策略防止惊群效应指数退避exponential优于线性退避linear死信队列不是可选项失败任务必须有归属通过removeOnFail保留或单独队列承接并发上限保护下游起步应保守再逐步上调任务数据保持精简传 ID 而不是完整对象降低 Redis 内存压力优雅关闭防止孤儿任务正确处理 SIGTERM。这些原则直接映射到技能 Capabilities 清单bullmq-queues、job-scheduling、delayed-jobs、repeatable-jobs、job-priorities、rate-limiting-jobs、job-events、worker-patterns、flow-producers、job-dependencies。二、工具链选型技能的 Tooling 部分给出了从核心依赖到运维监控的完整选型核心bullmq队列主库、ioredisRedis 客户端托管upstash、redis-cloud、elasticache、railway按需选择托管 Redis监控bull-board、arena、bullmq-pro可视化队列看板模式delayed-jobs、repeatable-jobs、job-flows、rate-limiting、sandboxed-processors沙箱化处理器。Scope 部分同时划清了职责边界redis-infrastructure交给redis-specialist、serverless-queues交给upstash-qstash、复杂workflow-orchestration交给temporal-craftsman、event-sourcing交给event-architect、email-delivery交给email-systems——即本技能只负责队列本身的工程实现不做跨界包揽。三、核心模式实战从入门到 Job Flow3.1 基础队列搭建生产就绪配置技能给出的基础示例涵盖了 Queue、Worker、QueueEvents 与共享 Redis 连接import { Queue, Worker, QueueEvents } from bullmq; import IORedis from ioredis; // 所有队列共享同一个连接 const connection new IORedis(process.env.REDIS_URL, { maxRetriesPerRequest: null, // BullMQ 必需项 enableReadyCheck: false, }); // 带合理默认值的队列 const emailQueue new Queue(emails, { connection, defaultJobOptions: { attempts: 3, backoff: { type: exponential, delay: 1000, }, removeOnComplete: { count: 1000 }, removeOnFail: { count: 5000 }, }, }); // 带并发上限的 Worker const worker new Worker(emails, async (job) { await sendEmail(job.data); }, { connection, concurrency: 5, limiter: { max: 100, duration: 60000, // 每分钟 100 个任务 }, }); // 事件监听 worker.on(failed, (job, err) { console.error(Job ${job?.id} failed:, err); });要点解析maxRetriesPerRequest: null是 BullMQ 的硬性要求否则 Redis 连接异常会导致 Worker 停止工作对应 Validation Checks 中的 ERROR 级检查defaultJobOptions将重试次数、指数退避、完成/失败保留策略固化到队列级避免每个任务重复配置removeOnComplete: { count: 1000 }/removeOnFail: { count: 5000 }用保留最近 N 条代替无限堆积控制 Redis 内存占用limiter实现队列级速率限制concurrency控制并发两者配合既保护 Redis 又保护下游服务数据库连接池、第三方 API 限流。3.2 延迟任务与定时Repeatable任务技能用三个调用覆盖调度场景// 延迟任务24 小时后执行一次 await queue.add(reminder, { userId: 123 }, { delay: 24 * 60 * 60 * 1000, // 24 hours }); // 定时任务每天 9 点执行显式时区 await queue.add(daily-digest, { type: summary }, { repeat: { pattern: 0 9 * * *, // 每天 9am tz: America/New_York, }, }); // 移除定时任务 await queue.removeRepeatable(daily-digest, { pattern: 0 9 * * *, tz: America/New_York, });两个关键坑位在技能 Validation Checks 中单独列出Repeatable job without explicit timezoneWARNING——不指定时区会用服务器本地时间跨夏令时DST会出现漂移因此tz参数应视为必填Retry without backoff strategyWARNING——有重试但没有退避会造成惊群效应。3.3 Job Flows多步骤任务编排与依赖FlowProducer 让父任务等待所有子任务完成成为一等公民import { FlowProducer } from bullmq; const flowProducer new FlowProducer({ connection }); // 父任务等待所有子任务完成后继续 await flowProducer.add({ name: process-order, queueName: orders, data: { orderId: 123 }, children: [ { name: validate-inventory, queueName: inventory, data: { orderId: 123 }, }, { name: charge-payment, queueName: payments, data: { orderId: 123 }, }, { name: notify-warehouse, queueName: notifications, data: { orderId: 123 }, }, ], });这是技能 Capabilities 中flow-producers与job-dependencies的具体落地库存校验、扣款、仓库通知三个子任务可以并行执行且分属不同队列父任务process-order会在全部子任务成功后才被触发天然实现多阶段、有依赖、可并行的复杂流程。结合原则 7子任务数据同样只传orderId这类 ID 而非完整对象。3.4 优雅关闭部署时零任务丢失Worker 直接被杀掉会留下孤儿任务技能的关闭流程是const shutdown async () { console.log(Shutting down gracefully...); // 1. 停止接收新任务 await worker.pause(); // 2. 等待当前任务执行完成可加超时 await worker.close(); // 3. 关闭队列连接 await queue.close(); process.exit(0); }; process.on(SIGTERM, shutdown); process.on(SIGINT, shutdown);顺序上有讲究先pause()停止消费再close()等待在途任务收尾最后关闭连接。技能在 Validation Checks 中将No graceful shutdown handling标记为 WARNING——缺失时部署/重启会造成任务孤儿化。3.5 Bull Board 可视化看板需要可见性时技能推荐 bull-board 系列import { createBullBoard } from bull-board/api; import { BullMQAdapter } from bull-board/api/bullMQAdapter; import { ExpressAdapter } from bull-board/express; const serverAdapter new ExpressAdapter(); serverAdapter.setBasePath(/admin/queues); createBullBoard({ queues: [ new BullMQAdapter(emailQueue), new BullMQAdapter(orderQueue), ], serverAdapter, }); app.use(/admin/queues, serverAdapter.getRouter());挂载后即可在/admin/queues可视化查看队列状态、任务状态分布与失败详情与技能 Tooling 中的bull-board、arena对应。四、Validation Checks把经验固化为可执行检查技能最有工程价值的产出是 11 项代码检查含严重级别与告警文案可直接沉淀为 Lint 规则或 Code Review 清单检查项级别核心信息Redis 连接缺少maxRetriesPerRequestERROR缺省会导致 Redis 异常时 Worker 停摆无 stalled 事件处理器WARNINGstalled 任务提示 Worker 崩溃应监控无 failed 事件处理器WARNING失败任务应记录日志并告警无优雅关闭处理WARNING部署时任务可能被孤儿化请求处理器中 await queue.addINFO建议 fire-and-forget 以加快响应任务数据可能过大WARNING传 ID 而非完整对象控制 Redis 内存任务无超时配置INFO建议设置 timeout 防卡死有重试但无退避策略WARNING应使用指数退避防惊群定时任务未指定时区WARNING服务器本地时间会随 DST 漂移Worker 并发可能过高INFO确认下游DB 连接、API 限流能承受请求处理器阻塞入队INFO入队应异步、快速返回这些检查与第三节的代码模式一一对应可作为代码写完自检一遍的 checklist。五、协作栈与其他技能组合的实战编排技能的 Collaboration 部分定义了委托触发词与多技能工作流体现了本仓库技能组合的工程理念委托触发触发词 → 目标技能redis infrastructure|redis cluster|memory tuning→redis-specialist队列依赖 Redis 基础设施serverless queue|edge queue|no redis→upstash-qstash不想自管 Rediscomplex workflow|saga|compensation|long-running→temporal-craftsman超出简单 Job 的编排event sourcing|CQRS|event streaming→event-architectdeploy|kubernetes|scaling|infrastructure→devopsmonitor|metrics|alerting|dashboard→performance-hunter。Email Queue Stackbullmq-specialistemail-systemsredis-specialist1. Email request received (API) 2. Job queued with rate limiting (bullmq-specialist) 3. Worker processes with backoff (bullmq-specialist) 4. Email sent via provider (email-systems) 5. Status tracked in Redis (redis-specialist)Background Processing Stackbullmq-specialistbackenddevops1. API receives request (backend) 2. Long task queued for background (bullmq-specialist) 3. Worker processes async (bullmq-specialist) 4. Result stored/notified (backend) 5. Workers scaled per load (devops)AI Processing Pipelinebullmq-specialistai-workflow-automationperformance-hunter1. AI task submitted (ai-workflow-automation) 2. Job flow created with dependencies (bullmq-specialist) 3. Workers process stages (bullmq-specialist) 4. Performance monitored (performance-hunter) 5. Results aggregated (ai-workflow-automation)Scheduled Tasks Stackbullmq-specialistbackendredis-specialist1. Repeatable jobs defined (bullmq-specialist) 2. Cron patterns with timezone (bullmq-specialist) 3. Jobs execute on schedule (bullmq-specialist) 4. State managed in Redis (redis-specialist) 5. Results handled (backend)技能还声明了推荐搭配redis-specialist、backend、nextjs-app-router、email-systems、ai-workflow-automation、performance-hunter。六、触发条件与使用边界When to Use当用户提到bullmq、bull queue、redis queue、background job、job queue、delayed job、repeatable job、worker process、job scheduling、async processing等关键词时触发。Limitations务必遵守仅当任务与上述 Scope 明确匹配时使用本技能技能输出不能替代环境特定的验证、测试或专家评审当缺少必要输入、权限、安全边界或成功标准时停下来向用户澄清。总结bullmq-specialist技能把 BullMQ 生产实践浓缩为一套原则—模式—检查—协作四层体系8 条设计原则指导心智模型5 组代码模式覆盖入队、调度、依赖编排、优雅关闭与可视化11 项 Validation Checks 把经验固化为可执行的自查清单4 个协作栈展示了如何与redis-specialist、email-systems、devops等技能组合解决真实业务问题。对于要在 Node.js/TypeScript 中落地 Redis 任务队列的开发者本文档可作为从 0 到生产可用的完整参考。【免费下载链接】agentic-awesome-skillsAAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,600 agentic skills. Includes CLI, local MCP, catalog, plugins, and Workbench.项目地址: https://gitcode.com/GitHub_Trending/an/agentic-awesome-skills创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考
平方复杂度无法被常规优化消除｜TaoToken 统一 Key 通道实测)
