title: Best practice to organize authorization in microservice architecture?
body: <p>For example, I have 3 services:</p>
  
  <ul>
  <li>Authentication </li>
  <li>Seller</li>
  <li>Buyer</li>
  </ul>
  
  <p>Each of them got their own databases, models, services... etc</p>
  
  <p>Authentication service knows about users, user-groups, roles, permissions and creates token.</p>
  
  <p>Where should I store sellers/buyers entities? On Authentication service, or on Seller/Buyer services?</p>
  
  <p>How should Seller/Buyer services interact to create new seller/buyer entity?</p>
  
  <p>How should Seller/Buyer services check permissions?</p>
  
  <p>Seller and Buyer entities have some common fields: name, password, email..., but also each of them have their own additional fields.</p>
  
  <p>Seller and Buyer interact with each other.</p>