Hi Manu,

Your argument is very well written and is compelling.

If you get a chance, check out what Nicholas Paldino has to say on the
subject of WCF -vs- .Net Remoting.  From what I understand, his position is
that WCF supersedes .Net Remoting.

What do you think of his position?

Also, do you think .Net Remoting should be used for my scenario?  (Please
read and comment on my post "WCF using MVC/Observer Pattern")

Thanks,  Jeff

Hello Manu,

Talking about "Remoting is dead" means it's dead in the aspect of interprocess
communication in distributed systems and weak declarative support.

The tight coupling is not right approach for the SOA. Remoting is good for
tight cohesion inside SOA.
Another disadvantages is that a lot of changes are imperative, it means that
there is lack of support to extend functionality using attributes.

I found that WCF supersedes Remoting by all params, including performance.

So I see no reason to use remoting right now.

---
WBR,  Michael  Nemtsev [.NET/C# MVP].  
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

M> Remoting is still alive
M> Many people think and say that Remoting is dead. They say that
M> “strong
M> binding” is the way of the past.
M> This is not true!!!
M> SOA is a great thing, loose binding is the way to achieve friction
M> free
M> interaction between systems but it comes with a price, and the price
M> tag is
M> something to take into consideration.
M> With Remoting and strong binding we could pass objects by reference
M> between
M> processes. This capability is extremely powerful and should not be
M> thrown
M> away just because SOA is “IN” and Remoting is “OUT” today.
M> When Interaction between systems is what you need use WCF.
M> When you pass only data between entities that have explicit
M> boundaries WCF
M> and SOA is your thing… But when object should be shared across
M> processes do
M> use Remoting. It is great.
M> It is no wonder that many internal infrastructures in the .Net
M> framework
M> still use Remoting.
M> Remoting is alive it will be with us for a long time …
M> manu cohen-yashar
M>

Hi

SOA is as a great architectural style, but it comes with a price.
Loose coupling is great if you think about future integration, but for great
things you have to pay.
There are many scenarios where I would like the power of RPC and tight
coupling and thus would not want to pay the price for SOA. This is where
Remoting comes in.

Before implementing a service I think we should ask:
“Is it really a service?”
“Do we need it as a service?”
“What do we gain in our system from implementing the four tenets of SOA?”

Sometimes we will find out that we have a client and server but we do not
have a service. This is where Remoting comes in.

Remoting is not dead !!! It is an RPC implementation which is an
architectural alternative to SOA.

Manu Cohen-Yashar