communications app fails because port is already in use

[aminnaggar]

Thanks for creating this repo and video!

As I was following along with you I found it interesting that you never assigned the communications microservice a separate port from the backend microservice, and when I came to run it sure enough it failed due to the port being already in use.

I did a quick sanity check and cloned your repo only to hit the same error. I was easily able to work around that by setting a port but Im' really curious how did you get yours to work without having to do that?

[sMiter911]

Communication service does not use a port as the other services. It uses a transport: Transport.TCP in the app module. Unlike the other two that use ports 3000 and 3001

[SithumDev07]

@sMiter911 What about the analytics micro service?

[CoroTapia6191]

Same issue in analytics project