-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
Description
Feature Description
Add a new connection variable to separate the connectionLimit for master and slave
The Problem
Currently the slave and master should have same number of connections.
If we want to have a write intensive application we need to make sure the read is also supporting the same amount of connections.
For RDS unless we modify the number of connections or increase the read replica it is difficult.
If we can separate the Connection limit for slave and master it would be great.
For read replica if we want to increase the connection limit we must replicate the connection details multiple times since for RDS it is pointing to the load balancer instead of host
The Solution
If we can separate the Connection limit for slave and master to different variable in both case we can give the connection limit to what we want and solve the problem for mysql
Considered Alternatives
For slave we can replicate the connection details to suffix our use case but for master we need to make sure the slave is capable of supporting same number of connection as master
Relevant Database Driver(s)
| DB Type | Relevant |
|---|---|
aurora-mysql |
yes |
aurora-postgres |
no |
better-sqlite3 |
no |
cockroachdb |
no |
cordova |
no |
expo |
no |
mongodb |
no |
mysql |
yes |
nativescript |
no |
oracle |
no |
postgres |
no |
react-native |
no |
sap |
no |
sqlite |
no |
sqlite-abstract |
no |
sqljs |
no |
sqlserver |
no |
Are you willing to resolve this issue by submitting a Pull Request?
✅