What is the difference between WCF and a Web Services?

Asked

Viewed 1,173 times

11

I’ve always worked with Web Services, but lately I’ve seen a lot if you talk about WCF, hence my doubt.

What’s the difference between WCF and a Web Services?

Is there some improvement between one and the other or something that is best to use between them?

1 answer

13


Web Service is a general concept and WCF is a specific technology of Microsoft (.NET), so just so it is already very different.

Web Services usually use REST as basic mechanism. There are some rules, but it is very liberal as the data can be trafficked. Web service has nothing to do with XML. Can be used in any standard web technology. Web Service is not SOAP, it can work as SOAP.

WCF can communicate in various ways, it is a technology that tries, as far as possible, to abstract the various existing communication mechanisms, and one of them can be a web service. It is an extensive *framework that tries to be a SOA (Service Oriented Architecture). The nice thing about him is that you can change the Binding communication without changing "nothing" in the code.

Some mechanisms are TCP, UDP, Named Pipes, Peer To Peer, MSQM, and of course HTTP, among others, it is even possible to plug new ones. He’s not just an abstraction in communication, he tries to create a pattern of message exchange, like the web service does it too.

WCF was talked about 10 years ago, but not today, it is almost out of use. It is a heavy technology, difficult to learn, use and has problems of design. The idea is good, but it has been terribly implemented and some situations are too specific to take advantage of this abstraction. It has room for its use, but is more limited than was previously thought. It was created in the last days of megalomania in software development where it was believed that computers would evolve indefinitely and abstractions would always be winners. A lot of what you read about him is based on assumptions that weren’t proven or that only made sense 10 years ago.

Web Service is universal, WCF not, needs to have applications prepared for it. In fact the same is true with web services, but because it is a universal standard, it has better interoperability.

Some people like better than Service Stack, but even it can be too heavy and too difficult besides not being so universal.

WCF is essentially abandoned (still supported) and should look for another technology. The suggestion is to use gRPC.

  • Just out of curiosity: if I need to make in . NET a "remote method call" (RMI in Java), how do I do? It’s with WCF itself?

  • So Web Services is still better to use than WCF?

  • I improved on.

  • Cool. The talk, was in some companies I did interviews lately and jobs that required knowledge in WCF.

  • 2

    Whoever adopts WCF marries him, that’s why I talk to people so they don’t adopt modinhas, have to wait to mature, see if it’s all the same. https://www.reddit.com/r/stackunderflow/comments/6imnzj/%C3%A9_rid%C3%Adculo_como_as_modas_digitais_se_tornam_um/? ref=&shareref_source=link

Browser other questions tagged

You are not signed in. Login or sign up in order to post.