Q1.
Should I use WCF or web services (2 situations)? I have one web service that will be used by multiple clients and I will be using multiple URL’s that all point to the same basic web service – depending on clients needs – right now it is only used externally
and I don’t expect that to change. We have another web service that is used both internally and externally. Right now our network and web server are at the same location and we don’t expect that to change.
Q2.How much faster is it to use this new WCF service internally over our network (TCP) than internally with our old web service (HTTP)?
Q3. I heard WCF has a DataContract which is more like an object than a standard web service ??? What does this exactly mean?
Advantages of WCF that I have read about – what am I missing?:
WCF is more flexible and not tied to .NET remoting (more platform independent) if one of my servers is off-site (different network).
Service can run over TCP if on same network or Http and other protocols. E.g.: if a server is moved off-site onto a different network, the protocol change is just a configuration change not a major coding change.
Can run as web service, windows service, or from command prompt and not tied to web server
Has a DataContract which is more like an object than a standard web service.
Support for sending messages using formats other than SOAP, such as Representational State Transfer (REST).
Built-in support for the latest Web services standards (SOAP 1.2 and WS-*) and the ability to easily support new ones.
Useful if you have a web service that is used by multiple applications (internal or external) – why ???
More easily integrates with Active Directory. How?
Web service is more secure and easier to manage
more easily secure entire web service and all its web methods
more easily encrypt the entire two way message. i.e. more encryption
dvfp
Member
54 Points
44 Posts
Why should I use a WCF and not a web service in my situation?
Feb 21, 2012 01:51 PM|LINK
Q1. Should I use WCF or web services (2 situations)? I have one web service that will be used by multiple clients and I will be using multiple URL’s that all point to the same basic web service – depending on clients needs – right now it is only used externally and I don’t expect that to change. We have another web service that is used both internally and externally. Right now our network and web server are at the same location and we don’t expect that to change.
Q2.How much faster is it to use this new WCF service internally over our network (TCP) than internally with our old web service (HTTP)?
Q3. I heard WCF has a DataContract which is more like an object than a standard web service ??? What does this exactly mean?
Advantages of WCF that I have read about – what am I missing?:
Anna Sun
Participant
1798 Points
219 Posts
Re: Why should I use a WCF and not a web service in my situation?
Feb 23, 2012 05:40 AM|LINK
Q1:What wrong with the two web services?I think If it runs ok , you needn't to change it.
Q2:WCF is not faster. WCF is just a tech that easy to create maintain the web service.
Q3:DataContract means that the object can be serialized, such as sent by json.
These points are the key points why we choose to use WCF.
If you have any feedback about my replies, please contact msdnmg@microsoft.com
Microsoft One Code Framework