# Design pattern for router

**URL:** <https://community.apollographql.com/t/design-pattern-for-router/7813>\
**Category:** Schema Design\
**Tags:** federation, schema-design\
**Created:** [September 10, 2024, 5:06pm UTC](https://community.apollographql.com/t/design-pattern-for-router/7813 "2024-09-10T17:06:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mayank](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@Mayank](https://community.apollographql.com/u/Mayank)\
**Post date:** [September 10, 2024, 5:06pm UTC](https://community.apollographql.com/t/design-pattern-for-router/7813/1 "2024-09-10T17:06:35Z")

</div>

I have 5UI interfaces and all are accessing same backend but 1 UI is dedicated for operations staff, 1 UI is dedicated for end user and 2 UIs have mix of end user and operation staff.1 UI is for commercial end user. To maintain separation of duty and to avoid single point of failure, shall I create different router for retail end user, commercial end user and operation staff while keeping same subgraph? What is right design pattern while I am following federated design pattern.