Yes, that could also be one of quick solutions. The thing I am worried about unreliable Ecto.Repo is that supervisor seems should only be used to supervise critical component to application (see link) with expectation that if critical component fail repeatedly it should be escalated to supervisor (which is not behavior i want from DB B, as it’s non-critical), but Ecto.Repo would require supervision as part of it’s setup.
