Scaling out WCF, how to deal with callbacks?

Question

Suppose, I want to scale out (add more boxes) some WCF service. This looks pretty easy, set up load balancer that calls WCF services on multiple boxes using for example round robin algorithm.

However how to deal with situation when a WCF service have callback contract. When a client connects to some particular box, it receives events only raised by this computer WCF service instance. And I want client to receive events that were raised by any WCF service instance in group (cluster).

What is the best way to make WCF service know about events raised by other WCF service instances?

Some ideas: Multicast, broadcast, WCF NetPeerTcpBinding, Single server that subscribes to all WCF services in cluster (acting as event aggregate).

UPDATE: I have managed to create test system, using NetPeerTCPBinding as a mechanism to share events across servers. I haven't made a benchmark yet, but I feel that WCF P2P is to heavy for this tusk, I'm gonna implement UDP broadcast based event sharing system.

possible duplicate of [WCF Duplex Communications in a clustered environment](http://stackoverflow.com/questions/1206510/wcf-duplex-communications-in-a-clustered-environment) — Darin Dimitrov, Jan 27 '12 at 12:48

score 2 · Answer 1 · answered Feb 16 '12 at 03:33

I would implement this by setting up a MSMQ queue that each server can subscribe to, and when an event occurs that the other servers need to know about, the service can publish it.

I use a library called NServiceBus to make this entire process simple. NServiceBus is a full-featured library that uses MSMQ (among other transports) to create pub/sub messaging buses, which would exactly solve your problem. It is easy to use and has a fluent interface for configuration, subscription, and publishing.

I will come back and edit this post later with an example, but the NServiceBus website has plenty of documentation to get you started until then.

I like this idea, will try, I played a little with NServiceBus, but never used it in production. — Alex Burtsev, Feb 16 '12 at 05:33

score 0 · Answer 2 · answered Jan 27 '12 at 13:22

0

Have you considered messaging? Sounds ideal.

answered Jan 27 '12 at 13:22

Rocklan

7,888
3
34
49

I haven't done any messaging stuff in a while, you'd need to do some googling, but check out the publish and subscribe Design pattern, eg http://www.codeproject.com/Articles/34316/Topic-based-Publish-Subscribe-design-pattern-imple – Rocklan Jan 27 '12 at 13:32

Scaling out WCF, how to deal with callbacks?

2 Answers2