| Groups | Blog | Home |
dotnet web services : WCF vs Remoting
WCF or even better with WSSF. I notice that the WSSF guidance doesn't take web farms or application farms into account. I would like to do in WCF, what I have already done in .Net 1.1 remoting. (see "BackGround" below). So has anybody got links or documents or other info on how I can achieve this. I am looking for a "heads up" to other peoples research before I need to conduct my own. Background In .Net 1.1, I constructed a web farm involving more that 18 servers. 3 were "web page" servers, 5 were "web service" servers and 10 were "application" servers. I did this using .Net remoting and ASP.net. I used a "well known" software factory on the "appliction" servers and http binding and singlecall to the connect from the other type of servers . I also had Proxy Class on each server as a common interface. I also used Network load balancers (BIGIP) between WebPagesServers->ApplicationServers and webServicesServers->ApplicationServers. That was easy as it was all http URIs.
My understanding is that WCF isn't a replacement for Remoting, it's an
additional layer on top of remoting (or web services). [quoted text, click to view] "FrazGJF" <FrazGJF@discussions.microsoft.com> wrote in message news:1CA6B608-C098-43C3-8F46-3092066219D2@microsoft.com... >I am interested in getting more information on replacing .Net Remoting with > WCF or even better with WSSF. > I notice that the WSSF guidance doesn't take web farms or application > farms > into account. > I would like to do in WCF, what I have already done in .Net 1.1 remoting. > (see "BackGround" below). > > So has anybody got links or documents or other info on how I can achieve > this. I am looking for a "heads up" to other peoples research before I > need > to conduct my own. > > Background > In .Net 1.1, I constructed a web farm involving more that 18 servers. 3 > were > "web page" servers, 5 were "web service" servers and 10 were "application" > servers. > I did this using .Net remoting and ASP.net. I used a "well known" software > factory on the "appliction" servers and http binding and singlecall to the > connect from the other type of servers . I also had Proxy Class on each > server as a common interface. > I also used Network load balancers (BIGIP) between > WebPagesServers->ApplicationServers and > webServicesServers->ApplicationServers. That was easy as it was all http > URIs. >
Scot,
with all the WCF/remoting comparsions being bantered about, it seems that a WCF solution IS a replacement for remoting. My query is really about: How does one build a WCF application farm be it web or some other type? That is, how do you expose classes as objects in a software factory and then extend that factory when a new class is created... Then tie it all together so that it can be deployed into a SYSTEM test bed, a UAT test bed and THE Production system. [quoted text, click to view] "Scott M." wrote:
> My understanding is that WCF isn't a replacement for Remoting, it's an > additional layer on top of remoting (or web services). > > > "FrazGJF" <FrazGJF@discussions.microsoft.com> wrote in message > news:1CA6B608-C098-43C3-8F46-3092066219D2@microsoft.com... > >I am interested in getting more information on replacing .Net Remoting with > > WCF or even better with WSSF. > > I notice that the WSSF guidance doesn't take web farms or application > > farms > > into account. > > I would like to do in WCF, what I have already done in .Net 1.1 remoting. > > (see "BackGround" below). > > > > So has anybody got links or documents or other info on how I can achieve > > this. I am looking for a "heads up" to other peoples research before I > > need > > to conduct my own. > > > > Background > > In .Net 1.1, I constructed a web farm involving more that 18 servers. 3 > > were > > "web page" servers, 5 were "web service" servers and 10 were "application" > > servers. > > I did this using .Net remoting and ASP.net. I used a "well known" software > > factory on the "appliction" servers and http binding and singlecall to the > > connect from the other type of servers . I also had Proxy Class on each > > server as a common interface. > > I also used Network load balancers (BIGIP) between > > WebPagesServers->ApplicationServers and > > webServicesServers->ApplicationServers. That was easy as it was all http > > URIs. > > > >
"Scott M." <s-mar@nospam.nospam> wrote in
news:uE$inWs$HHA.4584@TK2MSFTNGP03.phx.gbl: [quoted text, click to view] > My understanding is that WCF isn't a replacement for Remoting, it's an > additional layer on top of remoting (or web services). Although Microsoft says that WCF is a complement for Remoting - in reality, WCF is remoting's replacement. For all intents and purposes - remoting is dead with .NET 3.0. If you're going to start a project, WCF is a very attractive alternative to remoting and supports many of the features that were lacking (i.e. bidirectional messages, authentication and authorization). However remoting does still have some advantages - the ability to use shared interfaces. WCF uses proxies methods instead ... and have similar limitations to a web service (i.e. no method overloading, no sharable interfaces, etc.). But overall, WCF is such a major enhancement that it the disadvantages are minor in comparison to the new features.
=?Utf-8?B?RnJhekdKRg==?= <FrazGJF@discussions.microsoft.com> wrote in
news:23088055-D602-4DD0-A9BE-5594914B991D@microsoft.com: [quoted text, click to view] > Scot, > with all the WCF/remoting comparsions being bantered about, it seems > that a WCF solution IS a replacement for remoting. > My query is really about: How does one build a WCF application farm be > it web or some other type? WCF can be hosted in IIS - so as long as your application is stateless, you can load balance it like any other web application. [quoted text, click to view] > That is, how do you expose classes as objects in a software factory > and then extend that factory when a new class is created... > Then tie it all together so that it can be deployed into a SYSTEM test > bed, a UAT test bed and THE Production system.
Ok So now that we have covered that...
Back to my original question: So has anybody got links or documents or other info on how I can achieve this(applicaton farming with WCF or WSSF). I am looking for a "heads up" to other peoples research before I need to conduct my own [quoted text, click to view] "Spam Catcher" wrote:
> "Scott M." <s-mar@nospam.nospam> wrote in > news:uE$inWs$HHA.4584@TK2MSFTNGP03.phx.gbl: > > > My understanding is that WCF isn't a replacement for Remoting, it's an > > additional layer on top of remoting (or web services). > > Although Microsoft says that WCF is a complement for Remoting - in reality, > WCF is remoting's replacement. > > For all intents and purposes - remoting is dead with .NET 3.0. > > If you're going to start a project, WCF is a very attractive alternative to > remoting and supports many of the features that were lacking (i.e. > bidirectional messages, authentication and authorization). > > However remoting does still have some advantages - the ability to use > shared interfaces. WCF uses proxies methods instead ... and have similar > limitations to a web service (i.e. no method overloading, no sharable > interfaces, etc.). But overall, WCF is such a major enhancement that it the > disadvantages are minor in comparison to the new features. >
[quoted text, click to view]
"FrazGJF" <FrazGJF@discussions.microsoft.com> wrote in message news:811E77A8-3EC6-482A-94B9-72AEAED86C6D@microsoft.com... > Ok So now that we have covered that... > Back to my original question: > So has anybody got links or documents or other info on how I can achieve > this(applicaton farming with WCF or WSSF). I am looking for a "heads up" > to > other peoples research before I need to conduct my own I found an MSDN article on "Load Balancing" at http://msdn2.microsoft.com/en-us/library/ms730128.aspx. -- -------------------------------------------------------------------------------- John Saunders | MVP – Windows Server System – Connected System Developer
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |