An effective set of services open over a remote .NET network using more channels or endpoints?

Question

I am using a remote connection via TCP to prototype a distributed server application, where I want to have different services that can be opened from each process of a remote remote server.

In some cases, I want services to run from the same process, but I don't want all services to be used for this.

I am wondering if it is more efficient to have multiple services in the same process through the same remote access channel that differs in the URI / URL of the endpoint, or do I need to create new channels on different ports for each service in the same process?

Using ports is not so much a problem as the number of services will be low, and the network and machine configuration will be fully controlled.

It is also unclear to me if the remote send sends a URI string for each individual message or only during the connection, and regardless of whether the smart infrastructure is enough to reduce work if calls are made on the same machine and even in the same process

Thanks in advance.

Answer 1

You can also host separate processes on the same port using the Net.Tcp port exchange service.