Compatibility and security

Compatibility depends on the complete application path: database engine and version, client driver, protocol behavior, session patterns, workload, and network topology. CacheDB provides native proxies for PostgreSQL, MySQL, SQL Server, IBM Db2, and Oracle.

Validate the intended workload

Test the application’s real drivers and representative queries, transactions, prepared statements, data types, and error handling. Use transparent mode to observe the path before enabling cache reuse. The downloadable compatibility briefs summarize the database-specific considerations for an initial review. For details about your driver and workload, contact us.

Protect database connections

Native database paths support TLS 1.2 or later on both the client-to-proxy and proxy-to-database legs. Backend certificates are verified by default. Plaintext connections require explicit configuration. Cache connections do not support transport TLS, so keep the cache within a trusted network or protect it with network-level encryption.

Secure console access

The console should sit behind a TLS-terminating reverse proxy or WAF with network access controls and request limiting. Protect credentials and configuration, use tenant-scoped access, and retain audit data according to operational requirements.

Consider cache consistency

Transparent mode observes traffic without serving or storing cached results. Full mode reuses only eligible reads selected by policy. Invalidation follows successful writes, but cache reuse can be eventually consistent; do not apply it to data requiring strict read-after-write behavior without workload-level validation.