C# WCF Dead or alive?
-
The MS folks (Who are in touch with us consulting things) , themselves recommended to move out of WCF long ago saying anything related to REST, will not be updated on WCF. WebAPI is the new way!. So we cleaned up our circus of REST on WCF and moved to WebAPI. You would love it! WebAPI is super cool and simple, for all the basic data transactions it's just more than enough!
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
Ok, then I'll do that instead next time.
Wrong is evil and must be defeated. - Jeff Ello
-
i see a lot of blog posts around the internet that says WCF is Dead, any other thoughts?
They are wrong. WCF is... DEADBORN. So it's hard to say "zombie is alive/not alive", it's just zombie who fed by MS money and enthusiasm of stupids. We already have more than enough - TCP/IP, SOAP, JSON-RPC and even Protocol buffers from Google students. WHY MORE?! I say why - to hold stronger your eggs on MS hooks. Period. No any tech reason exist to jump on another "order of bytes in a stream".
-
i see a lot of blog posts around the internet that says WCF is Dead, any other thoughts?
I see a lot of stupid statements on the Internet. While it is certainly true that WCF has fallen out of the shiny favor. But that is far from dead. Many of those probably believe that soon everything on the internet will be done through a restful http interface.
-
:laugh: You are the man. That has the potential to send posts to the Abyss! You should have really gone for a clear YATCITA!
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
YATCITA?
Cheers, Mike Fidler "I intend to live forever - so far, so good." Steven Wright "I almost had a psychic girlfriend but she left me before we met." Also Steven Wright "I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
-
YATCITA?
Cheers, Mike Fidler "I intend to live forever - so far, so good." Steven Wright "I almost had a psychic girlfriend but she left me before we met." Also Steven Wright "I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
-
As far as I know SignalR is something completely different. SignalR supports two way HTTP(S) requests using web sockets. WCF supports all sorts of communication (through configuration), like HTTP(S), pipes, SOAP, and can, in theory, be used on any host (IIS/WAS, Windows Service, do we have any other flavors?). Please correct me if I'm wrong.
Read my (free) ebook Object-Oriented Programming in C# Succinctly. Visit my blog at Sander's bits - Writing the code you need. Or read my articles here on CodeProject.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
Absolutely, much less named pipes and many different forms of authentication. WCF is a bit like XML or Microsoft Office. It can do sooooo much more than most people realize or what most people use it for. When you need it, it's really nice, but often difficult to learn and master. I've been hearing people calling RoR and jQuery dead, but I still find myself using jQuery once in a while.
-
Kevin Marois wrote:
Why do hot dogs come in packs of 10, but hot dog buns come in packs of 8??
Buy 8 packs of hot dogs, 10 packs of buns, and invite 80 79 friends for a BBQ. No leftovers.
I think we could get by with 4 packs of hot dogs and 5 packs of buns. 38 friends. I will have two please.
-
i see a lot of blog posts around the internet that says WCF is Dead, any other thoughts?
Alive and growing. We are just switching to it for our JSON communication and love it. The configuration is pretty easy now. Used to be harder but now it is simpler. It also has cool AOP features, such as that ability to manipulate all packets before the WCF service even sees it with a message inspector. SignalR might be simpler at first glance, but does it have such AOP features? Can I authenticate all web services in one piece of code without adding a single line of code in each of my services? The feature set of WCF is huge and pretty much blows away anything else on the market.
-
i see a lot of blog posts around the internet that says WCF is Dead, any other thoughts?
-
Alive and growing. We are just switching to it for our JSON communication and love it. The configuration is pretty easy now. Used to be harder but now it is simpler. It also has cool AOP features, such as that ability to manipulate all packets before the WCF service even sees it with a message inspector. SignalR might be simpler at first glance, but does it have such AOP features? Can I authenticate all web services in one piece of code without adding a single line of code in each of my services? The feature set of WCF is huge and pretty much blows away anything else on the market.
Can you give me some tutorial links please?
-
Alive and growing. We are just switching to it for our JSON communication and love it. The configuration is pretty easy now. Used to be harder but now it is simpler. It also has cool AOP features, such as that ability to manipulate all packets before the WCF service even sees it with a message inspector. SignalR might be simpler at first glance, but does it have such AOP features? Can I authenticate all web services in one piece of code without adding a single line of code in each of my services? The feature set of WCF is huge and pretty much blows away anything else on the market.
-
i see a lot of blog posts around the internet that says WCF is Dead, any other thoughts?
Personally I prefer message queues these days. Several people have mentioned SignalR, and the hub could be considered a broker of sorts I guess. I've recently used both RabbitMQ (via the EasyNetQ library) and NetMQ to build microservices. For [potentially] load balanced services over a network, I prefer Rabbit. For single-process service containers (sounds strange at first, but we use in-process microservices at work to make individual components completely self-contained, allowing parallel development by many teams) I like using NetMQ with inproc sockets. NetMQ is also capable of TCP connections but IMHO the monitoring tools are not as good as the ones available for Rabbit. So, to answer the original question - is WCF dead? I don't think so. I think it's similar to WPF; not dead, but nobody is really working on new features or improvements either.
-
Nagy Vilmos wrote:
any other thoughts?
Why do hot dogs come in packs of 10, but hot dog buns come in packs of 8??
If it's not broken, fix it until it is
-
Now why didn't I think I that? oh ya, I don't have 79 friends.
If it's not broken, fix it until it is
-
Nagy Vilmos wrote:
any other thoughts?
Why do hot dogs come in packs of 10, but hot dog buns come in packs of 8??
If it's not broken, fix it until it is
-
Yet Another Thread Careening Into The Abyss. Especially when it contains a bit of objectionalble materials :)
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
:thumbsup:
Cheers, Mike Fidler "I intend to live forever - so far, so good." Steven Wright "I almost had a psychic girlfriend but she left me before we met." Also Steven Wright "I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
-
Can you give me some tutorial links please?
Well, yes. I do happen to blog. Here is a 6 part series (using a Basic Authentication Token Service) that shows how to do JSON enabled web services. By part 3 you get the message inspector. Then in Part 6 you actually get an html/javascript client. [Authentication Token Service for WCF Services (Part 1)](http://www.rhyous.com/2015/02/05/basic-token-service-for-wcf-services-part-1)
