gRPC Multiple service instances on same port

[Cosmin]

Hello all,

I have the following processes communicating on the same PC:

P1, P2, P3.... all have the same service interface -> just different instances of the same service.

Client and server communicate on localhost port 10000 for example. Base on some information received from the client the server will start a new process P1. or P2, or P3..or how many it needs ( P1 - is actually a server that will start listening on localhost port 10001 for example )

Then the client will discuss directly with P1, P2, P3, ... depending on it's needs

The problem with this is that P1, P2, P3... beeing the same service, I cannot start them on the same localhost port, and because I might have a lot of these processes I will use a large amount of ports -> not a good practice.

Is there a better practice for this using gRPC? At the moment I couldn't find a solution for it or at least I didn't know what to search for.

The language: C++, the environment: Windows

Thank you!

Cosmin

[pixel...@gmail.com]

Unfortunately, there's currently no support for this on Windows. There is currently support for SO_REUSEPORT on Linux however.

[Cosmin]

Thank you for the info. Does anybody know if something like this will be possible in the future on windows?

[Radosław Korzeniewski]

Hello,

wt., 20 lip 2021 o 16:51 Cosmin <cosmin.co...@gmail.com> napisał(a):

Hello all,

I have the following processes communicating on the same PC:

P1, P2, P3.... all have the same service interface -> just different instances of the same service.

Client and server communicate on localhost port 10000 for example. Base on some information received from the client the server will start a new process P1. or P2, or P3..or how many it needs ( P1 - is actually a server that will start listening on localhost port 10001 for example )

Then the client will discuss directly with P1, P2, P3, ... depending on it's needs

The problem with this is that P1, P2, P3... beeing the same service, I cannot start them on the same localhost port, and because I might have a lot of these processes I will use a large amount of ports -> not a good practice.

What exactly do you want to achieve in this setup? If all P1, P2 and P3 are the exact same service (same binary) and you want to get a better concurrency by spawning multiple processes then the best solution would be to use a single process but multiple threads. In this case you can share the single service tcp port with multiple threads without a problem.

best regards

--

Radosław Korzeniewski
rado...@korzeniewski.net

[Kumar Rajan]

Cosmin,

Were you able to solve this issue? We have a similar situation and looking for info on how you solved this.

Thanks
KR

[Ahmed]

@Radoslaw that is not the case for NUMA machines where, ultimately, multiple instances of the the same service (one per NUMA node) would be the way to go.