Menu
I am working on a .Net website which is going to have 1000s of concurrent users.
I am thinking of keeping the business components on the app server and UI components on the web server. Database (MS SQL Server 2005) will be hosted on another server. I am planning to use the load balancing as well.
Given this, what's the best way of communication from web server to app server if I want to have the optimum application performance and scalability?
206
It is now superseded by Windows Communication Foundation (WCF), which is part of the . NET Framework 3.0. Like its family members and similar technologies such as Common Object Request Broker Architecture (CORBA) and Java's remote method invocation (RMI), .
NET Remoting has already been deprecated with the release of . NET Framework 3.0 in 2009 and is no longer available on .
NET Core and . NET 5 and later versions don't have support for . NET remoting, and the remoting APIs either don't exist or always throw exceptions on these runtimes.
WCF is defined as Windows Communication Foundation and is a part of . NET 3.0 framework. Web services can communicate with any application built on any platform, whereas a . NET remoting service can be consumed only by a .
You can check here a performance comparison between WCF and other communication technologies (including .Net remoting). The conclusion is : WCF is faster.
83
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
