title: How many controllers should a MS Web API microservice have?
body: <p>I'm trying to set up a small learning project with a microservice architecture. I'm just  wondering: how many controllers should a microservice have?</p>
  <p>At the moment I have two tables: books (title, language, category etc.) and author (first name, last name, birth date etc.). Each of them has an entity, a DTO, a repository and a controller.</p>
  <ul>
  <li>/api/books/</li>
  <li>/api/authors/</li>
  </ul>
  <p>For me it would totally make sense to have two controllers: BooksControllers and AuthorsControllers. Both are in the first microservice (in this case also WebApi project)</p>
  <p>Later on I will add a second microservice &quot;sales figures&quot;. It would container sales figures for the books (and maybe later on sales figures for other stuff).</p>
  <p>Is this a good approach?</p>