Blog
News, releases and articles about @imqueue. Page 3 of 6.
Type-safe service-to-service communication in TypeScript
End-to-end types across service boundaries are easy inside one process and hard the moment you cross a network. Here's how to keep them without hand-writing clients or maintaining a schema language.
read →Stop hand-writing and maintaining your microservice clients
Every service you call needs a client, and hand-maintained clients drift out of sync with the services they talk to. Here's why that happens, how to make the client fall out of the service, and what the generated approach costs.
read →Load balancing microservices without a load balancer
For internal service-to-service traffic, the load balancer you run and operate is often solving a problem a message queue solves for free. Here's the competing-consumers pattern, why pull beats push, and what you give up.
read →Do your Node.js back-ends really need service discovery?
Consul, etcd, DNS-SD — service discovery is a lot of machinery to stand up. Sometimes you genuinely need it; often you don't. Here's how to tell, and how a queue makes the question disappear.
read →Back-pressure for Node.js services
When a downstream service slows down, HTTP tends to turn that into a cascading failure. A queue absorbs the spike instead. Here's the difference, and the trade-offs to watch.
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