I am about to start a project that will serve as a simple message bus. Messages or events will be sent to it just waiting for a subscriber. The messages don't have to be stored, as I just want this as a pass-through for any subscribers for live data. The preferred delivery mechanism is a web request - REST/JSON.
In my recent work with Redis, I thought of this as a good candidate, but since we are predominantly a Microsoft shop am also thinking of WCF Service and Windows Service Bus.
Subscribers may not all be .Net clients, so I would like to keep that as versatile as possible, however out of the gate, .Net client connectivity will be first.
I would like to create the simplest implementation possible - no huge development time, as I want to spend most of that on the subscribers.
Suggestions welcome.
If you want to use Redis, take a look at Redis's publish / subscribe commands.
I'm not a .net person, but it looks like this link might steer you in the right direction: https://github.com/ServiceStack/ServiceStack.Redis/wiki/RedisPubSub
