How are you hosting the components ? COM+, service
What type of data R U passing between the components adn the web server ?

General tips:
   Use chunky and not chatty calls
   Remoting calls are expensive depending on frequency and payload

Later
http://weblogs.asp.net/mdavey/

Hi Matt!

Thanx for your initiative.

I m sending my whole understanding and architecure we have planned so
far.

please review and suggest in our scenario.

Where .NET Remoting comes in the norchio purpose system architecture?


In the proposed structure, all the business logic, third party
components and COMPONENT reside on the COMPONENT server i.e. called
Business Tier.

To make communication possible between Presentation Tier (i.e. from Web
Server) and Business Tier (i.e. from COMPONENT Server) across the
machines, .NET Remoting is required.

Our understanding about .Net Remoting?
??    The Business logic DLL or common interface should be deployed on both
side (Web Server and Component server).
??    Performance Overhead.   
o    Calling and responding time in case of synchronous processes.
o    Network bandwidth and amount of data transfer is more.
??    Coding will be increased.
??    Security will be implemented explicitly (only if we use TCP channel,
but in case of HTTP channel, it inherits the security of IIS and
ASP.NET). TCP channel security can be implemented through IPSec.

Analyzed Solution - I (With Remoting ?V Using HTTP Channel)
??    We can use .net Remoting without deploying business logic dll on the
web server by using the HTTP (SOAP formatter) which creates the proxy
object on the web server end and make call on the remote host object.
??    HTTP is inherently slower than TCP but more secure than TCP.

Analyzed Solution - II (Without Remoting)
??    We can use Multiprocessor web servers instead of using separate
COMPONENT server.
o    No need of .Net Remoting.
o    Performance will considerably be enhanced.
o    Calling and responding time will be short.
??    Same security will be applicable to the business logic as on the web
server.
??    Coding will be decreased.
??    No channel implementation is used.

Our Problem
1)    Performance Overhead
How we can control this on a site that has large no of transaction at
any point of time.

2)    Deployment,  maintenance and traceability
How we can deploy (replicate the dlls on both COMPONENT, Web Server).
What are the constraints involved in maintenance and updations of the
dlls.

3)    Is it required to have a replication of the dlls or common interfaces
on both server and client?

4)    Does this architecture have any security related problem which can be
suggested?

5)    Any recommended guidelines which we can follow?

Mehta K