I’m skeptical there should be multiple Repos at all.
Yes, that’s exactly the conclusion I’ve come to. When I started building the apps individually, it made sense for them to have their own Repo and database because it made it easy to dev and test in isolation and each app didn’t need to know about the umbrella at all.
In practice, however, those individual repos are inefficient when they all are pointed at the same database when they get run under the umbrella. The more efficient solution, which you outlined, is to have a repo shared by all the apps (most of the apps?). If one app needs to use a separate repo (e.g. something other than PostGres, or maybe just to point to a separate instance for reasons of performance/security/???), then it would be relatively simple to replace the shared App.Repo with a different adapter.
