Configuration
The configuration parameters passed to connectMicroservice depends on the transport we use. A transport is a combination of a client and server that work in unison to transmit microservice requests and responses between the NestApplication and NestMicroservice contexts. Nest.js comes with a number of built-in transports and provides the ability to create custom transports. The available parameters depend on the transport we use. For now, we will use the TCP transport, but will cover other transports later. The possible options for the TCP transport are:
- host: The host that is running the NestMicroservice context. The default is to assume
localhostbut this can be used if the NestMicroservice is running as a separate project on a different host such as a different Kubernetes pod. - port: The port that the NestMicroservice context is listening on. The default is to assume
3000, but we will use a different port to run our NestMicroservice context. - retryAttempts: In the context...
