c# - Message Broker or ESB? -

i have system relies on sockets provide callback capabilities gaming system. failover , scalability, possible user attached 1 socket while user on same team attached another.

when control message comes in, need check how many sockets need respond message; ie: if team members on 1 socket, 1 socket needs push message team members. conversely, if team members 'load balanced' across multiple sockets, sockets in question need push message out respectively connected members.

currently, using polling system queries custom db tables include socket id (guid) members connected socket. joined message itself, guranteed each socket processes message.

the big issue is, loathe polling!

the big question is, technology should in order accomplish efficiently? looked sql server dependency, looks keeps db connection open until query satisfied.

i have entertained msmq, seems allow 1 'subscriber', rules out multiple interested sockets.

i not sure open source esb. understand premise of esbs, how indicate 1 socket processed message, while has not yet processed message successfully.

then there whole message brokering system. sounds eerily dumbed down esb me.

i appeal enterprise architects me decide quandry.

kind regards