title: DDD with Microservices and Multiple inputs via REST and Message Queue
body: <p>I have an aggregate root with the business logic in a c# project. Also in the solution is a REST web.api project that passes commands / requests to the aggregate root to do work and handle queries. This is my microservice. Now I want some of my events / commands / request to come of a message queue. I'm considering this:</p>
  <ul>
  <li>Put a console app in the solution to listen for messages from a message queue. <em>Then reference the aggregate root project in the console app</em></li>
  </ul>
  <p>Is it a bad pattern to share &quot;microservice business logic&quot; between two services? Because now I have two &quot;services&quot; an api and a console app doing the work. I would have to ensure that when the business logic changes both services are deployed.</p>
  <p>Personally I think it is fine to do what I suggest, a good CI/CD pipeline should mitigate that. But are there any other cons I might have missed?</p>