Cross plugin compatibility

Footnotes

1. Use only one failover plugin (gdbFailover/failover/failover2) at a time. ↩

2. A custom endpoint is a single-region Aurora construct and does not apply to global databases, should not be combined with the gdb plugins. ↩ ↩² ↩³

3. The limitless plugin manages its own routing and is incompatible with this plugin. ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸ ↩⁹ ↩¹⁰ ↩¹¹

4. Blue/Green is not supported on Aurora global databases, should not be combined with the gdb plugins. ↩ ↩² ↩³

5. Use only one read/write-splitting plugin at a time. ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶

6. The simple read/write splitting plugins (srw, autoSimpleReadWriteSplitting, gdbSimpleReadWriteSplitting, gdbAutoSimpleReadWriteSplitting) manage their own connections between two fixed endpoints and are incompatible with plugins that resolve or re-point connections. ↩ ↩² ↩³ ↩⁴

7. auroraStaleDns and the initial connection plugin both act on the initial cluster connection and conflict. ↩

8. The initial connection plugin opens and verifies candidate connections in a retry loop with openConnectionRetryIntervalMs delays before returning, so the time connectTime records would include those retries and waits rather than the true connection latency. ↩

9. A Blue/Green switchover replaces the whole deployment, so a custom endpoint's hand-picked instance subset does not carry over. ↩

10. fastestResponseStrategy and limitless use conflicting host-selection mechanisms. ↩