I was reading through the comments on this amazing MS announcement.
Amongst them I found a sentiment of some posters: frustration that WCF was being "abandoned". For example.
Please support server-side WCF. If you don't, you're marooning entire classes of apps.
- Chris Benard
Having used WCF lightly in the past, I was completed flabbergasted that people were upset about it not getting ported to .NET 5. Honestly, I thought the tech was already abandoned by the larger community a while now.
Later someone linked a github issue about this, which was eventually locked for being too heated. I read through all the comments on the issue. I get that people are concerned about interop with legacy applications. But I still don't see why I would create a new WCF service in 2019 on .NET Core. In other words, why would you want to carry that tech forward into .NET 5?
A lot of comments said that it does a lot for you. But many of the features listed either weren't clear to me why I would use them, or were just bad ideas -- like cross service transactions (due to scalability/service-coupling problems). And another portion of them have more standard/interoperable alternatives.
I was just curious if someone who used it out there in internetland could give me a few scenarios where it really shined. For example, some people say scalability, but don't elaborate on what they mean. (Service-level scalability? Developer scalability?) Or hosting the same service on HTTP and UDP -- what scenario has you doing that? Etc.
I suspect there could be some scenario that I am missing (aside from legacy interop). And I genuinely want to understand the ways in which people use it that make it irreplaceable to them.
Is it a case of wanting to keep using the WCF abstractions that you took pains to learn? Or is there really some core scenario that nothing else covers? I saw several people mention this, but there seemed to be no clear example/explanation to that effect. I would love to see some.