Sunday, November 1, 2009

Deprecating Web Services



Few quick note on Migrating WSE 3.0 Web Services to WCF.


The benefits of migrating WSE 3.0 Web services to Windows Communication Foundation (WCF) include improved performance and the support of additional transports, additional security scenarios, and WS-* specifications. A Web service that is migrated from WSE 3.0 to WCF can experience up to a 200% to 400% performance improvement. WCF implements many advanced web services (WS) standards such as WS-Addressing, WS-ReliableMessaging and WS-Security



WCF has support for multiple protocols (TCP/IP, HTTP, PIPE, MSMQ etc.). ASP.NET Web Services has only http.

WCF can be hosted outside if IIS i.e.: can be hosted in managed windows applications, IIS, a Windows Service, and WAS (Windows Process Activation Service)

WCF provides customization such as event hooks into service start / end / init / custom global error Handling etc. etc.

WCF supports more of the WS-* standards than Web Services, unless WSE is used.

You can’t really do streaming or support atomic transactions etc in Web Services.

WCF supports multiple binding’s HTTP, WSHTTP, TCP, MSMQ etc. ASP.NET Web Services has only http.

It can control concurrency

It has AJAX Integration and JSON (JavaScript object notation) support

Web Services have no instance management, i.e. you cannot have a singleton web service, or a session-full web service. You can maintain state of web services but we all know how painful that is.

A Web Service supports only the HTTP Request-Reply model, while WCF supports simple, Request-Reply and Duplex channels.

WCF is an extensible platform.

WCF while very similar to Web Services also incorporates many of the features of Remoting and .NET Enterprise Services (COM+ Services Components).

It is flexible and extensible like Remoting only more so.

It is compatible like Web Services only more so.

It is feature rich like Enterprise Services only more so 



Directly from Wikipedia: WCF is designed in accordance with Service oriented architecture principles to support Distributed computing where services are consumed by consumers. Clients can consume multiple services and services can be consumed by multiple clients. Services typically have a WSDL interface which any WCF client can use to consume the service, irrespective of which platform the service is hosted on. WCF implements many advanced web services (WS) standards such as WS-Addressing, WS-ReliableMessaging and WS-Security.


The WCF unifies the various communications programming models supported in .NET 2.0, into a single model. Released in November 2005, .NET 2.0 provided separate APIs for SOAP-based communications for maximum interoperability (Web Services), binary-optimized communications between applications running on Windows machines (.NET Remoting), transactional communications (Distributed Transactions), and asynchronous communications (Message Queues). WCF unifies the capabilities from these mechanisms into a single, common, general Service-oriented programming model for communications.

WCF can use SOAP messages between two processes, thereby making WCF-based applications interoperable with any other process that communicates via SOAP messages.




In What situations should you choose WCF instead of XML Web Services?

My first answer could be: now that .NET 3.5 is out and now that we know that a WCF service could be exactly like an XML Web Service, all the new services should be implemented by using WCF.

However, for giving a more professional answer... J if you have a scenario where you plan that different client applications needs to consume your service with different protocols, WCF is recommended. You can write your WCF service and expose different endpoint protocols for every types of different applications that could consume the service. You can obtain a complete and flexible SOA solution...




-          Conversion could be approached in two ways:

o        Migrating Existing Web Services to WCF (Few Tradeoffs - TBD)

o        Scratch Code.



Quick Link on Direct Migration:


Integrating WCF with your existing ASMX Services

Convert existing WS to WCF


Thanks & Regards,

Arun Manglick || Senior Tech Lead


From: Brijesh Choubey []
Sent: Saturday, October 31, 2009 12:27 AM
To: Arun Manglik; Nitin Mankar; Prakash Sharma
Cc: Prasad Pande
Subject: FW: Deprecating Web Services



Let's discuss this sometime next week before me discussing with Donnie.





From: Owen, Donnie []
Sent: Friday, October 30, 2009 2:53 PM
To: Brijesh Choubey
Subject: Deprecating Web Services




We need to consider deprecating existing and future web services in favor of WCF services. When we discuss 5.0 changes for VGS/Desktop I’d like to explore this further.






Donnie Owen

Lead Architect



607 Saint Henry Drive

Brandon, FL 33511


813.494.2456  Mobile

813.651.3615  Office



The experience speaks for itself ™


No comments:

Post a Comment