title: Save to share rabbitmq user across applications?
body: <p>I have a project which consists of a RabbitMQ instance along with several independent components providing various services, all of which will be making use of RabbitMQ for event broadcasting. </p>
  
  <p>My question is whether or not, at the connection level, it's safe to use a single RabbitMQ user for every component. In other words, one RabbitMQ user for the logical "application". Or would it be better to create separate RabbitMQ users for each connection? Would doing so (or not doing so) cause/resolve any concurrency issues or other hiccups? Or would it not matter?</p>
  
  <p>Apologies if this seems obvious, I'm new to RabbitMQ and would rather design things properly up front than deal with unfamiliar headaches later down the road.</p>