Blog
News, releases and articles about @imqueue. Page 4 of 6.
Guaranteed message delivery: cost and when to use it
"Will I lose messages if a worker dies?" is the right question — and the answer is a trade-off, not a yes/no. Here's how guaranteed delivery works, what it costs, and how to choose per workload.
read →Cutting the boilerplate out of Node.js microservices
Most of a new service's first commit is ceremony — transport wiring, serialization, a client, CI, a Dockerfile. Here's where the boilerplate hides and how to stop writing it by hand.
read →Versioning microservices without breaking every caller
A change to one service's method quietly breaks the services that call it — and you find out in production. Here's how to make breaking changes loud at build time, which changes are actually safe, and how to handle the window where both versions are live.
read →Testing services that call each other
Integration tests that require every service and its infrastructure running are slow, flaky, and painful. Here's a layered approach that tests most of your logic without spinning up the world.
read →Internal APIs don't need to be REST
REST is a fine choice for public, resource-oriented APIs. For internal service-to-service calls it's often ceremony over a plain function call. Here's when to drop it and what to reach for instead.
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