@imqueue BlogArticles about message-queue RPC for Node.js & TypeScript microservices.https://imqueue.org/blog/2026-07-22T00:00:00Z@imqueuehttps://imqueue.org/RPC between Node.js microservices over a message queue — no HTTP, no gRPChttps://imqueue.org/blog/rpc-over-message-queue-nodejs/2026-07-22T00:00:00Z2026-07-22T00:00:00ZMykhailo Stadnykhttps://imqueue.org/blog/authors/mykhailo-stadnyk/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.Type-safe service-to-service communication in TypeScripthttps://imqueue.org/blog/type-safe-service-communication-typescript/2026-07-19T00:00:00Z2026-07-19T00:00:00ZSerhiy Morenkohttps://imqueue.org/blog/authors/serhiy-morenko/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.Stop hand-writing and maintaining your microservice clientshttps://imqueue.org/blog/stop-hand-writing-microservice-clients/2026-07-17T00:00:00Z2026-07-17T00:00:00ZSerhiy Morenkohttps://imqueue.org/blog/authors/serhiy-morenko/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 and how to make the client fall out of the service for free.Load balancing internal microservices without a load balancerhttps://imqueue.org/blog/load-balancing-microservices-without-a-load-balancer/2026-07-14T00:00:00Z2026-07-14T00:00:00ZMykhailo Stadnykhttps://imqueue.org/blog/authors/mykhailo-stadnyk/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 and what it removes.Do your Node.js back-ends really need service discovery?https://imqueue.org/blog/do-nodejs-backends-need-service-discovery/2026-07-12T00:00:00Z2026-07-12T00:00:00ZMykhailo Stadnykhttps://imqueue.org/blog/authors/mykhailo-stadnyk/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.Back-pressure for Node.js services (and why HTTP makes it hard)https://imqueue.org/blog/backpressure-nodejs-services/2026-07-09T00:00:00Z2026-07-09T00:00:00ZMykhailo Stadnykhttps://imqueue.org/blog/authors/mykhailo-stadnyk/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.Guaranteed message delivery: what it costs and when you need ithttps://imqueue.org/blog/guaranteed-message-delivery-cost/2026-07-07T00:00:00Z2026-07-07T00:00:00ZMykhailo Stadnykhttps://imqueue.org/blog/authors/mykhailo-stadnyk/"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.Cutting the boilerplate out of Node.js microserviceshttps://imqueue.org/blog/cutting-boilerplate-nodejs-microservices/2026-07-04T00:00:00Z2026-07-04T00:00:00ZSerhiy Morenkohttps://imqueue.org/blog/authors/serhiy-morenko/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.Versioning microservices without breaking every callerhttps://imqueue.org/blog/versioning-microservices-without-breaking-callers/2026-07-02T00:00:00Z2026-07-02T00:00:00ZSerhiy Morenkohttps://imqueue.org/blog/authors/serhiy-morenko/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 and coordinate releases across a fleet.Testing services that call each other — without booting the whole stackhttps://imqueue.org/blog/testing-microservices-without-the-whole-stack/2026-06-29T00:00:00Z2026-06-29T00:00:00ZSerhiy Morenkohttps://imqueue.org/blog/authors/serhiy-morenko/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.Internal APIs don't need to be RESThttps://imqueue.org/blog/internal-apis-dont-need-rest/2026-06-27T00:00:00Z2026-06-27T00:00:00ZAndrii Glushkohttps://imqueue.org/blog/authors/andrii/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.From monolith to services: a low-risk first extractionhttps://imqueue.org/blog/monolith-to-services-first-extraction/2026-06-24T00:00:00Z2026-06-24T00:00:00ZAndrii Glushkohttps://imqueue.org/blog/authors/andrii/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.Redis as a message bus: patterns beyond pub/subhttps://imqueue.org/blog/redis-message-bus-patterns/2026-06-22T00:00:00Z2026-06-22T00:00:00ZMykhailo Stadnykhttps://imqueue.org/blog/authors/mykhailo-stadnyk/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.@imqueue vs Moleculer: two takes on Node.js microserviceshttps://imqueue.org/blog/imqueue-vs-moleculer/2026-06-19T00:00:00Z2026-06-19T00:00:00ZAndrii Glushkohttps://imqueue.org/blog/authors/andrii/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.@imqueue vs NestJS microservices: framework vs transporthttps://imqueue.org/blog/imqueue-vs-nestjs/2026-06-17T00:00:00Z2026-06-17T00:00:00ZAndrii Glushkohttps://imqueue.org/blog/authors/andrii/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 and how they can work together.tRPC vs @imqueue: client–server types vs service–service RPChttps://imqueue.org/blog/imqueue-vs-trpc/2026-06-14T00:00:00Z2026-06-14T00:00:00ZAndrii Glushkohttps://imqueue.org/blog/authors/andrii/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.@imqueue/job vs BullMQ: a simple Redis job queue vs a feature-rich onehttps://imqueue.org/blog/imqueue-vs-bullmq/2026-06-12T00:00:00Z2026-06-12T00:00:00ZAndrii Glushkohttps://imqueue.org/blog/authors/andrii/Both are Redis-backed job queues for Node.js. @imqueue/job is small, safe-by-default and scheduling-capable; BullMQ is the feature-rich one. Here's an honest split — plus the thing @imqueue does that BullMQ doesn't.gRPC vs message-queue RPC for internal Node.js serviceshttps://imqueue.org/blog/grpc-vs-message-queue-rpc/2026-06-09T00:00:00Z2026-06-09T00:00:00ZMykhailo Stadnykhttps://imqueue.org/blog/authors/mykhailo-stadnyk/gRPC is the default answer for typed RPC — and a great one, especially across languages. For an all-Node.js back-end, routing RPC through a queue trades some of gRPC's strengths for a lot less infrastructure.Benchmarking @imqueue: throughput, delivery modes, and how to measure your ownhttps://imqueue.org/blog/benchmarking-imqueue-throughput/2026-06-07T00:00:00Z2026-06-07T00:00:00ZMykhailo Stadnykhttps://imqueue.org/blog/authors/mykhailo-stadnyk/Real measured throughput for @imqueue's message queue — ~200k msg/sec unreliable, ~120k guaranteed on a 24-core box — what the delivery modes cost, and a reproducible harness to measure the figures that matter: yours.