# Generated typed service clients

Source: https://imqueue.org/blog/topics/clients/

Articles on generated typed service clients: why hand-written microservice SDKs rot, how self-describing services replace them, and using clients as test seams.

4 articles tagged `clients`, newest first.

- [The contract your services already publish: contract testing for Node.js microservices](https://imqueue.org/blog/contract-testing-generated-clients/) — 2026-09-04, Serhiy Morenko: Contract testing exists because two services can agree on a shape today and disagree on it next Thursday, with nothing in either repository to notice. If your clients are generated, most of that machinery is already built for you — and the part that is left is not the part the tooling advertises. Here is what an @imqueue service publishes about itself, how to pin it in a test that needs no broker, and the one place the contract can quietly disagree with your TypeScript. — [markdown](https://imqueue.org/blog/contract-testing-generated-clients/index.md)
- [Stop hand-writing and maintaining your microservice clients](https://imqueue.org/blog/stop-hand-writing-microservice-clients/) — 2026-07-17, 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, how to make the client fall out of the service, and what the generated approach costs. — [markdown](https://imqueue.org/blog/stop-hand-writing-microservice-clients/index.md)
- [Cutting the boilerplate out of Node.js microservices](https://imqueue.org/blog/cutting-boilerplate-nodejs-microservices/) — 2026-07-04, 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. — [markdown](https://imqueue.org/blog/cutting-boilerplate-nodejs-microservices/index.md)
- [Testing services that call each other](https://imqueue.org/blog/testing-microservices-without-the-whole-stack/) — 2026-06-29, 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. — [markdown](https://imqueue.org/blog/testing-microservices-without-the-whole-stack/index.md)

## Other topics

- [Message queues](https://imqueue.org/blog/topics/queue/) — 16 articles
- [RPC](https://imqueue.org/blog/topics/rpc/) — 14 articles
- [Architecture](https://imqueue.org/blog/topics/architecture/) — 11 articles
- [Patterns](https://imqueue.org/blog/topics/patterns/) — 11 articles
- [Comparisons](https://imqueue.org/blog/topics/comparison/) — 9 articles
- [Developer experience](https://imqueue.org/blog/topics/dx/) — 8 articles
- [Type safety](https://imqueue.org/blog/topics/types/) — 7 articles
- [Performance](https://imqueue.org/blog/topics/performance/) — 6 articles
- [Resilience](https://imqueue.org/blog/topics/resilience/) — 6 articles
- [Transports](https://imqueue.org/blog/topics/transport/) — 6 articles
- [Message delivery](https://imqueue.org/blog/topics/delivery/) — 5 articles
- [Jobs & scheduling](https://imqueue.org/blog/topics/jobs/) — 4 articles

All articles: [https://imqueue.org/blog/](https://imqueue.org/blog/) — [markdown](https://imqueue.org/blog/index.md)