Question

I’m looking for a pub/sub mechanism that can be used by .NET applications running on the same machine (a mixture of different app domains and processes). I’d really rather avoid having to run a separate service or anything that requires too much configuration. Obviously I’d like to keep the memory and cpu load to a minimum too.

Specifically I want to broadcast high volumes of small messages to subscribers on the same host. So I want a bus (e.g. MSMQ or NServiceBus) – but I don’t want the overhead of full network support (it only needs local named pipes) or the cost and complexity of an enterprise bus.

Answer 1

Named pipes is the fastest way to do local process interaction.

Reference:
NamedPipeServerStream
NamedPipeClientStream
Choosing a transport

Important reading:
Don’t get in a deadlock