Global cluster limitations with New Global writer end point

[bhanurhce]

Hello - Thanks for an outstanding wrapper software built around the JDBC driver.

It is regarding the usage of wrapper with Global cluster(Multi-AZ), we tested thoroughly with multiAZ regional failovers. Also, the new Global writer, in both cases the Wrapper plugin for Aurora PostgreSQL seamlessly detected the new writer DNS and we didn't require to restart the Applications pods. We saw application failures while the failover times, however, once the writer is available Application was able to pick the new writer without any pod restarts. Our questions is, are the limitations in using the wrapper with the Global cluster is still a concern and if we tend to use it, any idea on what would be the major unforeseen issue?

Thanks!