title: Building a Play framework module for sharing a data layer among several services
body: <p>Keeping the notion of a SOA in mind, my intent is to provide several different services, which leverage the same data model.  Imagine a poker application - we may have the following services:</p>
  
  <ul>
  <li>Game frontend</li>
  <li>Administrative frontend</li>
  <li>Player rank / leaderboard service</li>
  <li>Player finances service</li>
  <li>Bank integration service</li>
  <li>...</li>
  </ul>
  
  <p>All of these services can leverage the same model (perhaps providing additional model information where neccessary).</p>
  
  <p>In the Play! framework, is it possible for me to externalize this data model, but maintain the benefits we gain from using Play.  For example, runtime re-compilation.</p>
  
  <p>Modules seem like they might serve the job, but there is little documentation about them, and the examples given suggest the opposite paradigm - where services are the modules, and the core play application pulls in features.</p>
  
  <p>Any guidance would be appreciated.</p>