title: Registering DbContext in API Gateway
body: <p>Using Ocelot I have created an API Gateway. Sitting behind this API Gateway I have 2 other microservices which require the ability to do simple CRUD transactions. These services are:</p>
  
  <ul>
  <li>Customer.Api </li>
  <li>Identity.Api</li>
  </ul>
  
  <p>I have a separate DAL which contains a DbContext, entitites, repository and services. My plan is to inject the interfaces for these data access services into Customer.Api or Identity.Api so they can be used by the controllers. </p>
  
  <p>However, should the DbContext be added on the Gateway or would it require to be added to both services (Customer and Identity) in order to use the DAL repositories? </p>
  
  <p>If the DbContext needs to be added on every microservice wouldn't this be considered overkill? </p>