title: In microservices architecture, a service for common features should be common or not
body: <p>The question is related to microservices, when I have multiple microservices offering features/services that will be ordered and are billable.</p>
  
  <p>I am in fix as to which approach to take, </p>
  
  <p>a) An order and a billing service per billable microservice with their own respective databases.
  b) A common order management and billing service across all microservices.</p>
  
  <p>One thing that bothers me is that each billable feature/service has a different billing criteria / discounts.</p>
  
  <p>Observing some architectures, came across the following- <a href="https://d1jnx9ba8s6j9r.cloudfront.net/blog/wp-content/uploads/2018/02/Microservice-Architecture-Of-UBER-Microservice-Architecture-Edureka-768x762.png" rel="nofollow noreferrer">https://d1jnx9ba8s6j9r.cloudfront.net/blog/wp-content/uploads/2018/02/Microservice-Architecture-Of-UBER-Microservice-Architecture-Edureka-768x762.png</a></p>
  
  <p>in a blog- <a href="https://dzone.com/articles/microservice-architecture-learn-build-and-deploy-a" rel="nofollow noreferrer">https://dzone.com/articles/microservice-architecture-learn-build-and-deploy-a</a></p>
  
  <p>It depicts billing as a common and very centric to the entire architecture.</p>
  
  <p>Your insights will be highly appreciated.</p>