What the performance benefit is of switching from net.tcp to named pipes binding?
Asking since we have had some problems getting named pipes to work, and therefore wondering if it is worth the effort.
In chapter one of Programming WCF Services, Juval Lowy provides this flowchart for choosing the right binding:
Please see:
A Performance Comparison of Windows Communication Foundation (WCF) with Existing Distributed Communication Technologies - MSDN article.
What is the best choice for .NET inter-process communication?
WCF Binding Performance
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With