There's lots to read out there on this topic, but recently I've been confused about the discussions about the support for Remoting in Indigo, so I thought I'd ask for some help here..

So, we've developed a base framework here at the port that's getting a good deal of re-use.  We've got solid, stateless single-call business objects, all being reused from a slew of endpoint applications. The problem is that each time we deploy one of the endpoints, we're re-deploying the business tier, and all of its dependent .dlls, configuration, etc.  Needless to say, we're getting to the point where we need to consolidate our services, so that we can simplify their management and deployment, and scale them up, when needed.

I've seen this day coming (hence the stateless single-call business model) but now that it approaches, I've run into some confusion about which model of inter-process communication to use: Remoting or Web Services.  From everything I've read (1, 2, 3), it looks like the general gist of things has been the following: If your client endpoints are .NET and performance is a concern, use Remoting, otherwise, use Web Services.

But, then I ran across the following article about the future changes to Remoting that will accompany Indigo.  As to when to use what, this is what they say:

• Use .NET Remoting for calling between components hosted in different app-domains inside the same process
• Use .NET Remoting for handling custom wire protocols and formats.

It goes on to say: “However, we recommend minimizing your use of .NET Remoting to these niche areas, and suggest that you utilize ... ASMX/WSE for exposing your services at your boundaries.“

So, I'm kinda confused.  I want to use Remoting.  It seems like it will be simpler, faster and easier to code.  We've had some good success with Web Services, but from what I can tell, managing changes to web services over time is going to involve more work, will create more network traffic and will be slower overall.  So, other than the “Use Web Services because it'll work better with Indigo” (which isn't very compelling, btw) what compelling reasons do I have for using Web Services internally for inter-process communication accessing my buisness objects? 

Is anyone out there doing this one way or the other successfully?  Can you offer any advice?

Thanks in advance,

Brendan