Hi Pablo,
The good part is that only a database connection is required for sending and receiving messages with nginn-messagebus, so 1433 port is sufficient.
But I wonder if the pub-sub communication model implemented in nginn-messagebus is good for your case. NGinn-messagebus handles distribution of messages from publisher queues to subscriber queues so a simple use of pub-sub in your case would mean that every client app would have to run its own queue and to subscribe for events at all other queues, which is very impractical. The more workable approach would rather use a single central queue where the events would be sent by every application, and then distributed to all subscriber queues. Maybe I could suggest something if you gave more information:
1. Is the number of client applications fixed, or does it change?
2. Are the client applications running all the time (services/daemons) or are they only running when somebody's using them?
3. If a client app is inactive (not running), is it still interested in receiving event notifications that were generated during inactivity time, or can these events be ignored?
Best regards
R