Stefan, > A third option could be to add something between database client and > server. Something on layer 4 like multiple HAProxy servers or simple NAT > gateways. Or more complex on layer 7 specfic products like ProxySQL or > MaxScale. They could even pool connections and reduce the load on the > database server. But this all adds complexity and new ways to fail. > > The easiest solution in terms of implementation and operation is the one > Mark suggested: add multiple ip addresses and/or ports to your database > listener. > > Regards, > > Stefan >
My original idea was to add multiple source IPs to the app server. Mark's suggestion is similar, except we would change the destination IPs. Either way, it opens up the opportunity to have more unique sockets. Both suggestions would work. I'm just wondering if there is something I can do with network namespaces that would be even better. I don't have any experience with using it. -Eric Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
