final quiver
Hi, I'd like to have the input of people who have extensively worked with microservices the way NestJs intended.
I've been working for about a year and a half at a company that uses NestJS microservices. I just recently reread the nestJS microservices documentation and realized that we've not been using the Clientproviders at all, instead we've just been setting up HttpServices for inter-microservices communications.
(This was done years ago due to a lack of Gateway, since controllers needed to be exposed, they decided to have it all be http to avoid hybrid transport modes).
In short:Is the refactor worth it? Right now, things are working alright, but I'm still wondering about what benefits it could bring to do microservices the "Nest" way, using TCP messages for request-response exchanges (be it code simplicity, reliability, speed, or whatever). Which is why I'd like to hear about the experiences of people who are regularly doing microservices this way.
Thanks in advance for your feedback.
tough current