title: Dropwizard: handling multiple dropwizard instances
body: <p>As I'm developing micro-services using Dropwizard I'm trying to find a balance between having many resources on one running instance/application of Dropwizard versus many instances. </p>
  
  <p>For example - I have a project-A having 3 resources. In another project-B I would like to use one of the resources in project-A. The resource in common is related to user data. 
  Now I have options like : </p>
  
  <ul>
  <li>make http call to user resource in project-A from project-B. I can use client approach of dropwizard here</li>
  <li>as user resource is common - I can take it out from project-A to say project-C. And the I need to create client code in both project-A and project-B</li>
  <li>i can extract jar containing user code and use in project-B. this will avoid making http calls.</li>
  </ul>
  
  <p>Another point where I would like to have expert opinion is how to balance/minimize network calls associated with communication between different instances of microservice. In general should one use http to communicate between different instances? or can any other inter-process communication approach be used for performance perse [particularly if different instances are on same system]? </p>
  
  <p>I feel this could be common problem/confusion for new comers in the world of micro-services. And hence would like to know any general guideline or best practices. </p>
  
  <p>many thanks</p>
  
  <p>Pradeep</p>