Transport-Agnostic Messaging in NestJS

Understand how ClientProxy.send() behaves and why message patterns stay transport-agnostic.

In a NestJS microservice client, you call `this.client.send('sum', payload)` but the corresponding `@MessagePattern('sum')` handler never runs. Assuming the transport connection is healthy, what is the most likely cause?