CoreWCF VS MagicOnion

In the later versions you could avoid almost all the XML mess by configuring all of the settings in code. The experience is pretty close to gRPC imo, one plus point is you don't need to learn how to write proto classes. Though you could use protobuf-net for a similar experience. I'm kinda hopeful with CoreWCF, they aim to support more transports (including event gRPC) in the future along with queues other than MSMQ and slowly evolve from being too SOAP specific. There's a lot of potential still for WCF to be a transport agnostic framework that ecompass a lot of transports.

There's ongoing work on adding generic queue support. The first two concrete implementations should be MSMQ and RabbitMq from what I recall, though MSMQ will be windows only. But the nice thing about the work is it also opens up other types of message queues for WCF (e.g. Azure Service Bus, RabbitMq, Amazon SQS etc...).

The ongoing .net core port called CoreWcf plans to realize that goal as a future feature on it's roadmap. Where there's plans on adding new transports that didn't exist on .net framework wcf like Grpc, Azure Service bus, Amazon SQS, rabbitmq etc...

If you hit any difficulties or have any problems, feel free to jump on the gitter channel. Details for that are in the repo contributing guide.

Site URL Website https://corewcf.net/ Source Code https://github.com/CoreWCF/CoreWCF Announcements https://github.com/CoreWCF/announcements

WCF is part way there too via CoreWCF: https://github.com/CoreWCF/CoreWCF

Did you look at this project? It seems well maintained: https://github.com/CoreWCF/CoreWCF

There's Core WCF at least if you have existing services as a migration path. We're waiting for it to have a stable release and check if it supports all the bindings we need so we can move some of our WCF services to .Net6+.

If you're in dotnet land, I'd recommend poking magic onion [0] or messagepack. It'll be much nicer to work with once you have a decent pile of message types. Otherwise it's easy to end up in an entity framework like situation where you're constantly serializing and deserializing, generating serializer wrappers, etc. Although any of the cysharp libs are great in dotnet, definitely recommend checking out their back catalogue.

[0] https://github.com/Cysharp/MagicOnion

Having used it on a previous project, I found maintaining the protocol buffers quite tiresome. However, if I wanted to use it again, I'd be inclined to look into the MagicOnion project, which, in its own words:

MagicOnion? https://github.com/Cysharp/MagicOnion