Database compatibility
Native proxies for five database protocols.
Each CacheDB proxy speaks the database’s own wire protocol to the application and database. Keep the driver and SQL you already use; point the connection at the proxy and validate the exact versions and workload.
Native proxy matrix
Choose the protocol your application already speaks.
Compatibility depends on the client driver, database release, protocol features and workload. A technical evaluation should cover the exact connection path you plan to operate.
| Database | Client protocol | Proxy | TLS | Compatibility note |
|---|---|---|---|---|
| PostgreSQL | PostgreSQL | cdb-proxy-pgsql | TLS 1.2+ on both legs | SCRAM clients set channel_binding=disable. |
| MySQL | MySQL | cdb-proxy-mysql | TLS 1.2+ on both legs | Client and server compression are not supported. |
| SQL Server | TDS | cdb-proxy-mssql | TDS TLS; strict TDS 8.0 | Integrated authentication support depends on the driver. |
| IBM Db2 | DRDA | cdb-proxy-db2 | TLS 1.2+ on both legs | Db2 for z/OS requires customer qualification. |
| Oracle | TNS/TTC | cdb-proxy-oracle | TCPS on both legs | Native Network Encryption is refused; use TCPS. |
Download compatibility briefs
Review the database-specific requirements.
Each brief is available as a PDF for sharing with your application and database teams.
Evaluation requirements
Verify the complete connection path.
Test prepared statements, transaction patterns, data types, session settings, result sizes and error handling with the production driver and representative workload. The native proxy certificate and database certificate chain must match your trust configuration. Cache connections require a protected network path because transport TLS is not supported.
Review security boundariesCompatibility discussion
Bring the database and driver details.
We can map your client protocol, backend version, TLS requirements and operational constraints to an evaluation plan.