How many long-lived SSL connections can be supported on a BIG-IP LTM?
We have BIG-IP LTM devices on-prem.
A recent mandate stated that connections coming from a public cloud provider to an on-prem database must be encrypted across the entire public part of the connection. One proposed approach was to encapsulate the JDBC connection in SSL at its source (a VM in the public cloud), and then use the on-prem BIG-IP device to terminate the SSL, and forward the JDBC traffic over the on-prem network to the on-prem database.
Somebody suggested that the BIG-IP device would be limited in the number of connections that it could support, since JDBC connections tend to be very long lived compared to HTTPS connections.
Can anybody confirm whether we could use an F5 for this purpose, and give me an idea of how many concurrent connections a BIG-IP device might be able to support?