CODEWITHSUNDEEP
c#wcfperformanceremoting
Jeremy Thomson
Jeremy Thomson

Reputation: 999

.Net Remoting vs. WCF

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?

Upvotes: 14

Views: 8712

Answers (4)

Eduardo Xavier
Eduardo Xavier

Reputation: 1540

I've a project using 2 application servers and 2 front-end servers plus load balance: No problem at all. Runs fast like a thought.

The other team on my company is working in the same infrastructure. They have lots of problems... specially security ones!

Upvotes: 0

Nick
Nick

Reputation: 5908

We use net.tcp bindings with hardware load balancing on our high traffic sites. It seems to work great and we haven't had any problems with it.

Upvotes: 5

ybo
ybo

Reputation: 17152

You can check here a performance comparison between WCF and other communication technologies (including .Net remoting). The conclusion is : WCF is faster.

Upvotes: 18

Henk Holterman
Henk Holterman

Reputation: 273179

.NET remoting is more or less 'deprecated', it has been dissolved into WCF. So it's not an either/or question. I suppose you should ask: what kind of WCF (binding) or whether there are other alternatives.

Upvotes: 10

Related Questions