title: Microservice Architecture design for subscription
body: <p>Would like to get some opinion on designing a system with subscription model using microservice architecture. </p>
  
  <blockquote>
    <p>We implemented an identity server which authenticates and authorizes
    users, and stores their subscription profile. (i.e. resources they can
    access like which magazine and issues)</p>
    
    <p>on the resources service, the subscription profile will be used to
    filter their eligibility. example, if their subscription starts from
    Year 2018, then this will take effect and return only year 2018 data
    to the users via REST API.</p>
  </blockquote>
  
  <p>Is this a standard/proper microservice architecture implementation? or any better ways to design this?</p>