WCF or custom socket architecture

Question

I am writing a client / server architecture where, perhaps, hundreds of clients will work on several virtual machines, mainly on the intranet, but elsewhere.

Each client will collect data continuously and send a message to the server every second or so . Each message is likely to contain about 128 characters.

My question is that for this architecture, where I write both the client / server in .NET, should I work with WCF or some socket code that I wrote earlier. I need scalability (which means socket code), reliability, and just the ability to handle many messages.

Answer 1

I would not make a final decision without formulating any proof of concept. Create a very simple service, post it and use the stress test to get real results. Then confirm the results according to your requirements. You mentioned the number of messages, but did not indicate the expected response time. A similar issue is currently being discussed on the MSDN forum , which complains about the slow response time of WCF compared to sockets.

Other requirements are not directly mentioned in your post, so I will make some assumptions about better performance:

• netTcpBinding - , , .NET-/. , Net.Tcp, .
• , - . , .
• , . TCP- , -, -. - .
• , .

. WCF net.tcp ( ), (bcause ).

Answer 2

100 WCF, . WCF , , .

, , WCF .

Answer 3

From my experience with WCF, I can say that high-load performance is very pleasant. In particular, you can choose between several bindings to achieve your requirements for different scenarios (httpBinding for external communication, netPeerTcpBinding on the local network, for example).