I would like to suggest to rename the MasterSlaveConnection extension to something more sensible.
My suggestion would be PrimaryReplicaConnection, since that's one version of naming alternatives for the concept that is widely used (https://en.wikipedia.org/wiki/Master/slave_(technology)#Terminology_concerns).
Since this part of the code is primarily concerned about managing connections between writable and readable database replicas it could also be named WriteReadConnection, though IMO that could be a bit more misleading.
IF this and a specific naming is agreed upon by the team, I would take on the code part of this change.
For b/c an alias for the old class name could be kept around at least for a bit of time.
I would like to suggest to rename the MasterSlaveConnection extension to something more sensible.
My suggestion would be
PrimaryReplicaConnection, since that's one version of naming alternatives for the concept that is widely used (https://en.wikipedia.org/wiki/Master/slave_(technology)#Terminology_concerns).Since this part of the code is primarily concerned about managing connections between writable and readable database replicas it could also be named
WriteReadConnection, though IMO that could be a bit more misleading.IF this and a specific naming is agreed upon by the team, I would take on the code part of this change.
For b/c an alias for the old class name could be kept around at least for a bit of time.