This is a very common question that comes in our mind. We already have so many technologies for inter or intra process communication(distributed technologies), then why do we need the WCF? Why Microsoft
working in this side. One of the design goals of WCF is to unify the way distributed systems are developed prior to release of .Net Framework 3.0.
Each technology has their own restrictions
working in this side. One of the design goals of WCF is to unify the way distributed systems are developed prior to release of .Net Framework 3.0.
Each technology has their own restrictions
- Asp.net web service(ASMX) : It can not work with other protocols like MSMQ & Named Pipe and it can be hosted in IIS only.
- Web Service Extensions(WSE): WCF is much more configurable and has good interoperability features with non .net clients. WSE is the enhancement over web service and has some performance issue.
- MSMQ: It is just an protocol which is used to send only message then your service will pick the message from Queue and process further. It work like fire and forgot model.It doesn't have inter interoperability capabilities. Where WCF is the framework, you can develop services which can communicate through lot's of protocol, MSMQ can be one. WCF replace the MSMQ messageing api which was used in pushing and popping messages using a queue.
- .Net Remoting: It works only .net environment
- .Net Enterprise Service(ES): It works only .net environment
Comments
Post a Comment