Evaluate
Getting started with CacheDB
Understand the request path, transparent operation, and the questions to answer in a CacheDB evaluation.
CacheDB is a database proxy with an optional result cache. It sits between an application and its database, observes requests, and can serve eligible reads from a shared Redis Community, Valkey, or Redis Enterprise cache when an explicit policy permits it. The source database remains authoritative.
Follow a request
Every CacheDB proxy speaks a native database protocol. The application connects to the proxy using its existing database driver; CacheDB then handles the request and connects to the configured database.
In transparent mode, requests continue to the database while CacheDB parses traffic and records operational context. Cache lookups and writes remain off. This lets a team check compatibility and workload behavior before enabling cache reuse.
In full mode, an eligible read may be served from the shared cache. A cache miss continues to the database and a successful result may be stored. Writes always reach the database; policy can invalidate cached results related to changed data.
| Operating mode | Cache result reuse | Useful for |
|---|---|---|
| Transparent | Disabled | Initial traffic observation and compatibility checks. |
| Full | Enabled for policy-approved reads | Measured workloads with reviewed freshness and invalidation rules. |
Start with representative traffic
Begin with one application path and note its database, client driver, query and write patterns, session behavior, and freshness requirements. Observe that path in transparent mode, then review query patterns and invalidation relationships in the console. Decide which reads are safe to reuse before moving to full mode.
Cache reuse can be eventually consistent. Do not cache data that needs strict read-after-write behavior without validating the consequences for that workload. Avoid using a cache for locks, sessions, rapidly changing flags, or data whose consumers require every read to reflect the latest database write.
Choose a compatible path
CacheDB provides native proxies for PostgreSQL, MySQL, SQL Server, IBM Db2, and Oracle. Confirm supported database versions, drivers, TLS requirements, and deployment details in Compatibility & security.
Next, review deployment choices or how CacheDB works. You can also review the cache policy model and the multi-tenant console before planning a rollout.