title: NServiceBus & deciding service boundaries
body: <p>I am a beginner at NSB and I have been looking for some kind of rule of thumb for deciding what constitutes as a separate service. Unfortunately I haven't found much online or in <a href="https://www.packtpub.com/application-development/learning-nservicebus" rel="nofollow">David Boike's</a> book or on the <a href="http://docs.particular.net/nservicebus/" rel="nofollow">docs</a> page.</p>
  
  <p>The typical examples given are Sales, Shipping, Billing. So my original thinking is to divide according to real departments in a company, but what about things like Logging and other things that may fit into a 'fire and forget' model? Wouldn't having so many services increase the complexity? Is there a certain optimal number?</p>
  
  <p><strong>what is a good rule of thumb for deciding what is a real service without going over the top?</strong></p>