PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

Memory leak potential with Grpc

I saw the method getService from client-grpc.ts always re-create client that could lead to memory potentially. Also I saw method getClientByServiceName has been implemented by not being used by anywhere.

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

What is the current behavior?

My backend got issue when calling getService multiple times and I observed that memory has been increased constantly (I know that we should call getService only once when NestModule has been inited but there is exception for my codebase).

I've tested by calling thousand of grpc calls (that will call getService method) and here is the memory profiling.

Issue Number: N/A

What is the new behavior?

After changing createClientByServiceName by getClientByServiceName, the memory issue has been solved, no more memory increasing occur.

Does this PR introduce a breaking change?

• Yes
• No

Other information