Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Has anyone developed a decent naming convention for MSMQ queues when using NServiceBus, where there are many queues on a single server, but also on other servers?
The system I’m developing will have many discrete subscbribers across a set of servers, and some of the servers will run multiple unrelated applications.
It would be nice to be able to open the msmq management console and immediately know the purpose for all the queues.
Cheers
I’m sure you’ll find as many different ways to do this as you’ll find developers.
We don’t really have any non-NServiceBus queues, so we have no need to prefix them “nsb_” like Adam Fyles suggested.
We like to do a dot-separated notation that roughly mimics class namespaces, like “ProjectName.QueueName”.
Or for really big projects, where there’s more Udi-style service boundary analysis going on, we’ll do something more like “BigProjectName.ServiceName.QueueName”.
We have an NServiceBus cluster that runs our distributors, and this is where we locate our error queue, so every endpoint uses something like “Error@NSBCluster”. This enables us to monitor the system from one place.