Blog
News, releases and articles about @imqueue. Page 5 of 6.
From monolith to services: a low-risk first extraction
You don't migrate a monolith by rewriting it. You extract one capability, keep everything else in place, and repeat. Here's a concrete, low-risk first step for a Node.js team.
read →Redis as a message bus: patterns beyond pub/sub
Most people know Redis pub/sub and stop there. Redis has richer primitives — lists, blocking pops, and streams — that make it a capable message bus. Here's a tour, and where each fits.
read →@imqueue vs Moleculer: two takes on Node.js microservices
Moleculer is a full-featured microservices framework with many transporters; @imqueue is a focused, TypeScript-first RPC layer over a message queue. Here's an honest comparison to help you pick.
read →@imqueue vs NestJS microservices: framework vs transport
NestJS is a full application framework with a microservices module; @imqueue is a focused RPC transport. They're not really competitors — here's how they differ, where each is stronger, and how to run them together.
read →tRPC vs @imqueue: client–server types vs service–service RPC
tRPC gives you end-to-end types between a frontend and its backend. @imqueue gives you typed RPC between backend services over a queue. They solve adjacent — not competing — problems.
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