This post originated from an RSS feed registered with .NET Buzz by Robert Hurlbut. Original Post: Improving .NET Application Performance and Scalability, Beta 3 Feed Title: Robert Hurlbut's .Net Blog Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/rhurlbut/Rss.aspx Feed Description: Development with .Net, Rotor, Distributed Architectures, Security, Extreme Programming, and Databases Latest .NET Buzz Posts Latest .NET Buzz Posts by Robert Hurlbut Latest Posts From Robert Hurlbut's .Net Blog

I think I have been asleep a couple of times and missed that Beta 3 of Improving .NET Application Performance and Scalability (which I mentioned back in December, 2003) was released on February 27, 2004.

Looking at the chapter on Remoting, I noticed this comparison (which wasn't in Beta 1 and Beta 2):

Web Services vs. Enterprise Services vs. Remoting

The following are product team recommendations for choosing a communication technology:

*    Use Remoting for one process, cross application domain communication, or if you need to integrate with a legacy protocol.

*    Use Web services wherever you have a boundary to cross.

*    Use Enterprise Services inside your service implementation if you need a component service such as distributed transactions.

Web services are the recommended approach for crossing boundaries. Some common boundaries include servers, trust domains, organizations and teams. You should also use Web services for single machine inter-process communication.

If you have some kind of boundary that leads you to use Services but you have a performance problem, then you should use Enterprise Services.

If you haven't looked at this best practice guide on peformance before, do so now.  Noticeably, .Net performance expert Rico Mariani has contributed a lot to make this very good resource to be a great resource!