title: Inheritance across micro-service entities in Domain Driven Design
body: <p>I have a system, of micro services.
  A serviceH manages books.
  A serviceM manages magazines.</p>
  <p>They provide RESTful interfaces to work with their entities.</p>
  <p>Book domain and magazines domain - are different domains, as books and magazines are distributed and promoted totally differently.</p>
  <p>Still there are cases, where some clients want to handle all printable media, as a generalization of books and magazines equally:
  Link those against shelf's, manage their authors etc.</p>
  <p>Is it a good idea, introduce a printable media service, to model  actions, properties, common for books, magazines?</p>
  <p>So that a new printed-media can be introduced to this generalization, without touching the code for linking against shelfs?</p>
  <p>Worth other words: how to handle inheritance in Domain Driven Design?</p>