web api – Repository Pattern to support Bounded Context

I am building a REST Api from scratch so i am overthinking and revisiting various approaches and best practices.

I have a Materials repository that serve all the sub-domains of our logic.

Also i have a Sales and Inventory sub domains that both relate to the Materials.

I found this question that evolves exactly around what i am doing and after going and now another question arises for me in regards to Repository pattern.

Let’s consider the following REST Api routes:

  1. /masterdata/materials. Provide a list of materials and their master data.
  2. /sales/materials. Provide Sales per material in different granularoty.

Where the methods that satisfy /sales/materials have to be implemented?

In the Repository of Materials or in the Sales repository?