Allow Dataverse to work with secondary reads from a scaled database #4765
Description
With the recent containerization work, the postgres component added the ability to scale:
The problem now is that Dataverse isn't written to handle a scaled database. So in the above implementation, Dataverse is configured to only talk to the master instance of postgres. More work will need to be done in Dataverse to take advantage of the master slave setup to get any performance benefits. Namely handling primary vs. secondary reads. The implications could be widespread so using two datasources as a first step might be appropriate and switching over DB calls 1 by 1 to allow secondary reads will probably be the best approach.