.NET Framework Bookmark and Share   
 index > .NET Remoting and Runtime Serialization > How Scalable is .NET Remoting
 

How Scalable is .NET Remoting

I am creating a .NET Remoting application using a custombi-directional TCP channel and it will eventually have over 20000 client applications.

How scalable is .NET Remoting?
Dynamic
Hello,

I think this questionis a difficult one to answer.
It depends on network topology, hardware andmost importantlythe amount of data that you're remoting.

However, .NET remoting is the fastest way (that I know of)you can let your applications communicate with each other.
Any web solution will be slower because they usually use SOAP, which is an XML format.

I guess stress testing your application will tell how scalable it is.
Stefan H.F. A.
Thanks Stephen,

I think Socket Programming is faster than .NET Remoting but is more complex to setup and program maybe.

By scalability, I mean for instance can we apply load balancing when using .NET Remoting?

Thanks,
Dynamic
Hello,

here is an article that explains the possiblities of load balancing in .NET remoting:

http://support.microsoft.com/default.aspx?scid=kb;en-us;830217
Stefan H.F. A.
Thanks Stefan,

Apparently, load Balancing can only be applied for when using Singlecall SAO hosted in IIS.

Dynamic

You can use google to search for other answers

Custom Search

More Threads

• remoting exception, request service not found
• how to send SMS using c#.net ?
• MTOM issue? : MIME part with Content-ID not found
• How to create events?
• Returning a FileStream over a remoting connection
• "use" a wsdl (SOAP)
• Transfering large volume of binary data through the wire
• Connection limits and TcpServerChannel
• Run remote code as remote process identity
• Tips on remoting a Direct3D type