title: A microservices architecture design problem?
body: <h2>Problem background:</h2>
  <p>Currently, we are designing a unified authority mid-stage system for the group's business systems. Due to the large number of systems designed, the corresponding authority division business rules are fine. From the previous &quot;distributed across various business systems&quot;, it is now planned to be &quot;unified in the authority center Assign User Behavior. &quot;
  When doing architecture design, an architecture diagram is roughly divided as follows:</p>
  <p><a href="https://i.stack.imgur.com/qweMr.png" rel="nofollow noreferrer">Architecture diagram</a></p>
  <h2>Problems：</h2>
  <ol>
  <li>The lower-level services do not rely directly on each other. The upper-level aggregation services provide external services in a unified manner. This architecture can reduce the coupling between the lower-level services to a certain extent. But the existence of aggregation services has turned into a &quot;big collection&quot; and other systems; how should this step be optimized?</li>
  <li>After the aggregation service is unified, it becomes the main entrance of the business, and thus it is a single point. How should this step be optimized?</li>
  <li>Under this architecture, the upper-layer aggregation service feels like a gateway. Is there still a need for an ingress gateway?</li>
  </ol>
  <p>Thx~</p>