---
title: "#bullmq articles | Hashnode"
description: "Explore 57 articles tagged #bullmq on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/bullmq"
---

Tag

# #bullmq

57 posts · 2 followers

[Waseem Anjum](https://hashnode.com/@fabwaseem) · [Oct 28](https://hashnode.com/posts/postgres-job-queue-pg-boss-vs-bullmq/6ae1a1b5fc67f7b410fc8b91)

### [Postgres Job Queues in 2026: SKIP LOCKED vs pg-boss vs BullMQ (Redis and Postgres), Benchmarked](https://fabwaseem.hashnode.dev/postgres-job-queue-pg-boss-vs-bullmq?utm_source=hashnode&utm_medium=feed)

Enqueue speed, throughput, pickup latency, crash recovery, transactional enqueue and storage per job, measured on PostgreSQL 18.6 and Redis 8.0.2

20 min read · [fabwaseem.hashnode.dev](https://fabwaseem.hashnode.dev/postgres-job-queue-pg-boss-vs-bullmq?utm_source=hashnode&utm_medium=feed)

[Aditya Kumar Gupta](https://hashnode.com/@adityaguptareal) · [Oct 15](https://hashnode.com/posts/bullmq-with-node-js-and-redis/6ad034142082bca99ec2ea05)

### [BullMQ with Node.js and Redis](https://blog.adityaguptareal.com/bullmq-with-node-js-and-redis?utm_source=hashnode&utm_medium=feed)

The producer and worker can run in separate Node.js processes. They do not need to share JavaScript memory because they communicate through the queue

23 min read · [blog.adityaguptareal.com](https://blog.adityaguptareal.com/bullmq-with-node-js-and-redis?utm_source=hashnode&utm_medium=feed)

[Ryan Bell](https://hashnode.com/@shankproof) · [Oct 11](https://hashnode.com/posts/metrics-are-not-enough-adding-searchable-history-to-bullmq/6acc1c7a92ee2a35371dfc06)

### [Metrics Are Not Enough: Adding Searchable History to BullMQ](https://shankproof.dev/metrics-are-not-enough-adding-searchable-history-to-bullmq?utm_source=hashnode&utm_medium=feed)

How bull-der-dash grew an embedded SQLite history store, full-text search, and exact per-job-name stats — without reintroducing the Redis-scanning problem I warned about last time.

11 min read · [shankproof.dev](https://shankproof.dev/metrics-are-not-enough-adding-searchable-history-to-bullmq?utm_source=hashnode&utm_medium=feed)

[Ram Ji Tripathi](https://hashnode.com/@rjtdev) · [Oct 4](https://hashnode.com/posts/redis-bullmq-for-ai-workloads-retries-are-not-enough-you-also-need-idempotency-and-ordering/6ac285a4a9c4a2861076fd66)

### [Redis + BullMQ for AI Workloads: Retries Are Not Enough — You Also Need Idempotency and Ordering](https://rjt.hashnode.dev/redis-bullmq-for-ai-workloads-retries-are-not-enough-you-also-need-idempotency-and-ordering?utm_source=hashnode&utm_medium=feed)

Moving AI analysis out of an HTTP request improves the request path. Queueing that work does not make it correct. In my AI Support Assistant, a new message triggers BullMQ analysis of the ticket conve

16 min read · [rjt.hashnode.dev](https://rjt.hashnode.dev/redis-bullmq-for-ai-workloads-retries-are-not-enough-you-also-need-idempotency-and-ordering?utm_source=hashnode&utm_medium=feed)

[ZyVOP](https://hashnode.com/@zyvop) · [Sep 25](https://hashnode.com/posts/background-jobs-in-nestjs-with-bullmq-a-complete-walkthrough/6ab6a68fce8c09838c40e31a)

### [Background Jobs in NestJS with BullMQ: A Complete Walkthrough](https://blog.zyvop.com/background-jobs-in-nestjs-with-bullmq-a-complete-walkthrough?utm_source=hashnode&utm_medium=feed)

Move slow, occasionally-flaky work off the request thread — retries with backoff, durable status tracking, and idempotent re-enqueueing, built on NestJS, BullMQ, and PostgreSQL.

14 min read · [blog.zyvop.com](https://blog.zyvop.com/background-jobs-in-nestjs-with-bullmq-a-complete-walkthrough?utm_source=hashnode&utm_medium=feed)

[Chris Mowforth](https://hashnode.com/@m6h) · [Aug 24](https://hashnode.com/posts/announcing-invar-a-diskless-transactional-document-db/6a8cb861292e4c3857f5a890)

### [Announcing Invar: A diskless transactional document DB](https://blog.hardpoint.dev/announcing-invar-a-diskless-transactional-document-db?utm_source=hashnode&utm_medium=feed)

A new Redis-compatible DB, backed by S3

15 min read · [blog.hardpoint.dev](https://blog.hardpoint.dev/announcing-invar-a-diskless-transactional-document-db?utm_source=hashnode&utm_medium=feed)

[Olajumoke Boladale-lawal](https://hashnode.com/@Jutivia) · [Jul 19](https://hashnode.com/posts/scheduling-isn-t-a-timestamp-problem-it-s-a-reconciliation-problem/6a5c15fc4507358d9d4d300c)

### [Scheduling Isn't a Timestamp Problem, It's a Reconciliation Problem](https://jutivia.hashnode.dev/scheduling-isn-t-a-timestamp-problem-it-s-a-reconciliation-problem?utm_source=hashnode&utm_medium=feed)

A practical guide to job scheduling with BullMq (Redis)

5 min read · [jutivia.hashnode.dev](https://jutivia.hashnode.dev/scheduling-isn-t-a-timestamp-problem-it-s-a-reconciliation-problem?utm_source=hashnode&utm_medium=feed)

[Abhishek Batra](https://hashnode.com/@BatraAbhishek) · [Jun 26](https://hashnode.com/posts/i-stopped-using-redis-pub-sub-for-submission-notifications-in-my-leetcode-clone/6a3e5874a69552c33ce4ac27)

### [I Stopped Using Redis Pub/Sub for Submission Notifications in My LeetCode Clone](https://abhishek-codes.hashnode.dev/i-stopped-using-redis-pub-sub-for-submission-notifications-in-my-leetcode-clone?utm_source=hashnode&utm_medium=feed)

How BullMQ QueueEvents helped me keep my workers simpler, my API servers stateless, and my architecture horizontally scalable.

4 min read · [abhishek-codes.hashnode.dev](https://abhishek-codes.hashnode.dev/i-stopped-using-redis-pub-sub-for-submission-notifications-in-my-leetcode-clone?utm_source=hashnode&utm_medium=feed)

[Subramanya M Rao](https://hashnode.com/@Subramanya11) · [May 24](https://hashnode.com/posts/i-built-a-full-stack-llm-observability-platform-for-a-founding-engineer-take-home/6a130ab3551486ce6c0b95ed)

### [I Built a Full-Stack LLM Observability Platform for a Founding Engineer Take-Home](https://subramanyarao.hashnode.dev/i-built-a-full-stack-llm-observability-platform-for-a-founding-engineer-take-home?utm_source=hashnode&utm_medium=feed)

Every inference logged with zero hot-path overhead — SSE streaming, fire-and-forget ingest, and hourly rollups in PostgreSQL.

9 min read · [subramanyarao.hashnode.dev](https://subramanyarao.hashnode.dev/i-built-a-full-stack-llm-observability-platform-for-a-founding-engineer-take-home?utm_source=hashnode&utm_medium=feed)

[Rahul Boney](https://hashnode.com/@RAHULBONEY7) · [May 10](https://hashnode.com/posts/escaping-the-kafka-trap-scaling-a-node-js-event-pipeline-with-redis-and-bullmq/6a007b2ce3eebc2e2077feb0)

### [Escaping the Kafka Trap: Scaling a Node.js Event Pipeline with Redis and BullMQ](https://rahulboney.hashnode.dev/escaping-the-kafka-trap-scaling-a-node-js-event-pipeline-with-redis-and-bullmq?utm_source=hashnode&utm_medium=feed)

You probably don't need a massive Kafka cluster. Here is how I avoided over-engineering and built a hyper-resilient, zero-data-loss event pipeline using Node.js and Redis.

4 min read · [rahulboney.hashnode.dev](https://rahulboney.hashnode.dev/escaping-the-kafka-trap-scaling-a-node-js-event-pipeline-with-redis-and-bullmq?utm_source=hashnode&utm_medium=feed)
