title: Migrating multi-module project to microservices?
body: <p>I have multi module application. To be more explicit these are maven modules where high level modules depends on low level modules. 
  Below are the some of the modules :-</p>
  
  <pre><code>    user-management
      common-services
      utils
      emails
  </code></pre>
  
  <p>For example :- If <code>user management</code> module wants to use any services from <code>utils</code> module, it can call its services as dependency of utils is already injected under user-management.
  To convert/call my project truly following microserives architecture, I believe i need to convert each module as  independently deployable services where each module is a war module
  and provides its services over http(mainly as resful web services) . Is that correct or anything else need to be taken care of as well ? </p>
  
  <p>Probably each modules now has to be secured and authentication layer as well ?</p>
  
  <p>If that's the crux of microservices I really do not understand when someone ask whether you have worked on microservices as to me Its not tool/platform/framework but a simple 
  concept to divide you monolithic application in to smaller set of deployable modules whose services is available through HTTP. Is n't it ? May be its another buzz word.</p>
  
  <p><strong>Update:-</strong>
  Obviously there are adavantages going micro services way like independent unit testablemodule, scalable as it can be deployed on separate machine, loose coupling etc but I see I need to handle two complex concerns also </p>
  
  <ol>
  <li>Authentication:- For each module I need to ensure it authenticates the request which is not the case right now</li>
  <li>Transaction:- I can not maintain the transaction atomicity across different services which I could do very easily at present</li>
  </ol>