Fastest remoting channel in .NET

Question

5.00/5 (1 vote)

See more:

I am looking to achieve the fastest and scalable communication between several servers. I've developed a custom TCP socket server for this purpose with (IOCP) as I think it would be the fastest communication in .NET, but I don't know if it crashes on high load, or if my solution is the fastest communication channel for .NET applications. Is there any open source solution out there to meet my needs?

What's the fastest, scalable, reliable communication channel in .NET Applications?

Posted 30-Sep-10 6:56am

EhsanShemirani

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

ARopo · Answer 1 · 2010-09-30T22:54:00

Depends on your deployment

Everything on the same machine
Everthing on a LAN
Everthing over a WAN
Over the internet

Fastest would be tcpip, but this would present firewall problems if over a WAN.

Regarding crashing on high load that would depend on how well your software and infrastructure copes with high load, this is down to your design not so much the channel type you are using.

If you software need deploying in many different situations I would recommend leaving the channel type configuable.