title: Microservice solution structure in .NET applications
body: <p>I'm developing an application using the microservices approach, and I'm having a hard time defining how those microservices will look like on a visual studio project.</p>
  
  <p>My initial approach is to create one visual studio solution for every microservice. Every solution will have the following projects:</p>
  
  <ul>
  <li>Host</li>
  <li>Business API</li>
  <li>Data Access Layer</li>
  <li>Model</li>
  <li>Interfaces (for DI) </li>
  <li>Data Access Mock</li>
  <li>Tests for Business API</li>
  </ul>
  
  <p>So there are 7 projects per microservice. Somehow it feels a lot of projects being reimplemented for every solution.</p>
  
  <p>Is this approach correct? Has anybody built microservices with .net? How does your projects configuration look like?</p>