Blog
News, releases and articles about @imqueue. Page 2 of 6.
Auto-scaling Redis broker: with and without broadcast
One Redis behind your message bus is a ceiling and a single point of failure. The promoter and unicaster modules turn a fleet of plain Redis instances into a horizontally auto-scaling broker — here are the recipes for networks that deliver broadcast and for clouds like GCP that don't.
read →One isolated imq CLI home per @imqueue project
Every imq invocation shares one ~/.imq — one config, one pid registry, one set of logs. Here's how to give each project its own isolated CLI environment with IMQ_CLI_HOME, plus recipes for direnv, shell wrappers, per-client tokens and disposable sandboxes.
read →RPC over Redis in Node.js: patterns and pitfalls
How request/reply RPC over Redis actually works in Node.js — the correlation, timeout and delivery problems you have to solve yourself, why the old npm packages stalled, and how @imqueue turns it into typed, boilerplate-free calls.
read →BullMQ alternatives for Node.js: an honest 2026 guide
BullMQ is the default Redis job queue for Node.js — but it isn't the only choice. Here's an even-handed map of the alternatives (Bee-Queue, pg-boss, Agenda, @imqueue/job and more), what each is actually good at, and how to pick.
read →RPC between Node.js microservices over a message queue
Why route internal service-to-service calls through a message queue instead of HTTP or gRPC — and how @imqueue makes those calls fully typed with zero client boilerplate.
read →All articles
2026
- @imqueue vs NATS: a framework and a transport are not the same choice
- How Node.js services talk to each other in 2026: the honest options
- One notification, every replica: the LISTEN/NOTIFY duplicate problem
- Graceful shutdown and zero-drop deploys
- Delayed and scheduled work without adding a job system
- Auto-scaling Redis broker: with and without broadcast
- One isolated imq CLI home per @imqueue project
- RPC over Redis in Node.js: patterns and pitfalls
- BullMQ alternatives for Node.js: an honest 2026 guide
- RPC between Node.js microservices over a message queue
- Type-safe service-to-service communication in TypeScript
- Stop hand-writing and maintaining your microservice clients
- Load balancing microservices without a load balancer
- Do your Node.js back-ends really need service discovery?
- Back-pressure for Node.js services
- Guaranteed message delivery: cost and when to use it
- Cutting the boilerplate out of Node.js microservices
- Versioning microservices without breaking every caller
- Testing services that call each other
- Internal APIs don't need to be REST
- From monolith to services: a low-risk first extraction
- Redis as a message bus: patterns beyond pub/sub
- @imqueue vs Moleculer: two takes on Node.js microservices
- @imqueue vs NestJS microservices: framework vs transport
- tRPC vs @imqueue: client–server types vs service–service RPC
- @imqueue/job vs BullMQ: Redis job queues compared
- gRPC vs message-queue RPC for internal Node.js services
- Benchmarking @imqueue: throughput and delivery modes