When should I use Pipes or gRPC for interprocess communication (in C# .NET Core)?

Question

Both Pipes and ASP.NET Core gRPC support local and remote IPC/RPC (with some platform limitations for gRPC)

When would I use one technology (Pipes) or the other (gRPC)?

Observations, thoughts and considerations I'm keeping in mind:

• gRPC seems to be geared towards replacing WCF in some future iteration.

• local deployments and with machine restrictions (running as non-admin/user, machine firewalls, different platforms/OS)

• network traversal, and compatibility with same-machine -> multi-machine (frontend/backend arrays) for load and expansion

• Spanning secure zones (where a Proxy is used, or other TLS cipher/order/registry setting) affects the ability for HTTP/2 to work

• Pipes (named pipes?) have a different surface area and port (do they also use port 135, or NetBIOS over TCP (not sure of name))... how is it scanned and secured?

• "memory mapped files" seem to be a challenge to get working, however it seems to work in ASP.NET Core with gRPC in the UDS configuration. Is this a correct inference?

Right now my scenario is to have two console apps communicate with each other, same machine or remote. Adding Asp.NET Core Web is an optional front end alternative for my scenario.

Answer 1

Simple IPC

Depends on how much communication is going to happen. If your communication is limited to simple collaborative signal passing or sharing some data between two processes you can safely use NamedPipeClientStream and NamedPipeServerStream on local system or local network but if you plan for the same on different systems then I would suggest using TcpClient and TcpListener.

Comprehensive IPC

WCF or now its replacement gRPC is for scenario where a complete API/Framework need to be executed remotely. For example I have an entire library of classes which I need to call from a different process (which mostly run on a different system); in that case gRPC kind of solutions make more sense.

Only you can decide.

This is a design decision which is highly unique for your application; your future plans and your system environment and any third person can only give you clues but ultimately you are the only person who can make the right decision.