4 ms·
I suspect that WCF is mostly on its way out, but don’t quote me on that. There seems to have been little interest in continuing to support it.
by zenexer 7y ago
I suspect that WCF is mostly on its way out, but don’t quote me on that. There seems to have been little interest in continuing to support it.
- GordonS 7y agoI'm primarily a .NET developer - I haven't seen WCF used in a new project for maybe 10 years or so. It lost out to simpler, JSON-over-HTTP a long time ago, and good riddance!
- throwaway55554 7y agoOk, but surely that's not used for IPC.
- GordonS 7y agoNowadays many people do indeed use JSON over HTTP for IPC - it's the lifeblood of microservices. More efficient protocols are also used of course, such as Cap'n Proto, Protocol Buffers etc.
- throwaway55554 7y agoOk, I get if they're looking to scale and have them on multiple machines. But I tend to use namedpipes and/or shared memory because I need fast access between multiple services on the same machine. I don't need to scale.
- GordonS 7y agoYou can use named pipes without WCF[0]. Sample here[1]. I've also used the IpcServiceFramework[2] before, and it worked a treat. [0] https://github.com/dotnet/docs/blob/master/docs/standard/io/how-to-use-named-pipes-for-network-interprocess-communication.md https://github.com/dotnet/docs/blob/master/docs/standard/io/... [1] https://github.com/GustavoHennig/PipePoc https://github.com/GustavoHennig/PipePoc [2] https://github.com/jacqueskang/IpcServiceFramework https://github.com/jacqueskang/IpcServiceFramework