It think largely depends on the nature of the client environment and the level of abstraction you want to achieve. You can develop a solution as @skrealin suggests that directly interacts with the messaging infrastructure, but this is not really ideal for internet/web based clients who's connectivity/subscription cannot be guaranteed and may also require exposing your infrastructure unnecessarily. There are a couple of options I would consider investigating for these scenarios
- SignalR
- Azure ServiceBus
Both of these will provide "push" notifications and help manage subscriptions for your clients with straight forward api. A "polling" solution might nit be appropriate here because of the relatively high notification rate.
There are other approaches I'm sure, but looking at this will give you some sense of what's involved.